Skip to main content
VulnerabilityPublished Updated

CVE-2026-19434: maalfer Pentestify · Cross-site Scripting

Affects maalfer PentestifySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.1 Medium : upgrade to 2.3.1 when convenient.

Data as of 9 Nov 2026, 23:24 UTC

CVSS 4.0 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.3.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Upgrade maalfer Pentestify to 2.3.1.

Affected software

ProductAffectedFixed in
maalferPentestifyAffected
  • <2.3.1
Fixed in
  • 2.3.1
GitHubPentestifypkg:github/PentestifyOther threatsAffected
  • <2.3.1
Fixed in
  • 2.3.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade to version 2.3.1 or later once available, as this version presumably addresses the vulnerability. Until then, restrict access to trusted authenticated users and monitor for suspicious activity related to report rendering.

Description

Cross-site Scripting in the finding renderer in maalfer Pentestify before 2.3.1 allows authenticated users to execute arbitrary JavaScript in the application origin via HTML markup stored in a finding's severity field, which the frontend interpolates unescaped into class and style attributes when rendering the report.

References

Community reviews

Loading reviews…