CVE-2026-59238: Stored XSS in Pentestify via unsanitized finding images and report client logo
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-17 06:13 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
Stored Cross-site Scripting (CWE-79) in the client-side report rendering functions (renderPreview, renderEditor, renderAuditData in js/app.js) in maalfer Pentestify before 1.1.0 allows a remote, authenticated attacker to execute arbitrary JavaScript in the browser of any user who views an affected report via a payload stored in a finding’s images array or a report’s client_logo array, which is interpolated into an <img> src attribute without escaping.
Description quoted from the CVE record (assigned by Secur0, published 2026-07-20).
Weakness: CWE-79 Improper neutralization of input during web page generation (‘cross-site scripting’)
How it can be exploited
Exploitable over the network with low attack complexity with no special attack requirements needing no privileges and no user interaction. Impact: confidentiality none, integrity low, availability none. CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N
CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: yes. Technical impact: partial.
Public exploit evidence (Exploit Observer)
Exploit Observer found 3 code repositories naming this CVE.
Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.
See all 6 references on Exploit Observer
Live scores
- EPSS
- 0.006
low predicted chance of attack - VEDAS
- 0.989
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| Maalfer Pentestify | before 1.1.0 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Fixed versions stated in the CVE record: 1.1.0.
Vendor guidance:
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-59238 Pentestify - Stored Cross-Site Scripting via report images/client_logo. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-59238 Pentestify - Stored Cross-Site Scripting via report images/client_logo"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/api/reports"; nocase; fast_pattern; http.request_body; content:"image"; nocase; pcre:"/(onerror|onload|onmouseover|%3cimg|<img|%3csvg|<svg|%3cscript|<script)/i"; classtype:web-application-attack; reference:cve,CVE-2026-59238; reference:url,https://www.exploit.observer/?keyword=CVE-2026-59238&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=pentestify&match=exact; metadata:signature_type network_only; sid:1079203; rev:1;)
CVE-2026-59238.rules on GitHub
References
Vendor advisories and patches
Technical analysis and advisories
- https://secur0.com/en/cna/cve-list/cve-2026-59238-stored-xss-in-pentestify-via-unsanitized-finding-images-and-report-client-logo (technical-description)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners