CVE Tools

CVE-2026-109662

Frappe ERPNext before 15.112.0 Stored XSS via Public Portal Form

No known exploitation. No EPSS score yet. Fixed versions are out.

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • Frappe ErpnextAffected: < 15.112.0Upgrade to: 15.112.0Affected: ≥ 16.0.0-beta.1, < 16.23.0Upgrade to: 16.23.0Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check if you run Frappe ERPNext, and whether you have any public-facing portal forms enabled for customers or visitors.
  2. If you're on ERPNext 15.x, upgrade to 15.112.0 or later.
  3. If you're on ERPNext 16.x, upgrade to 16.23.0 or later.
  4. Until upgraded, consider disabling or restricting public portal forms that accept unauthenticated submissions.
  5. After upgrading, review recently submitted portal form records for suspicious script-like content.

What it is

From the CVE record

Frappe ERPNext before 15.112.0 and 16.x before 16.23.0 contains a stored cross-site scripting vulnerability in a public portal form that accepts unauthenticated submissions and stores content later rendered with insufficient neutralisation. Unauthenticated attackers can submit crafted markup that executes in the browser sessions of staff who review the stored record.

In plain language

Written by AI from the record

A flaw in ERPNext's public web forms before version 15.112.0 lets outsiders plant hidden code that runs when your staff view the submitted record, but this isn't being exploited anywhere and isn't an emergency.

Unauthenticated stored XSS in Frappe ERPNext's public portal form submission handler (CWE-79) allows attacker-supplied markup to persist and execute in staff browser sessions when the record is viewed, enabling session-level compromise within the portal context.

If you're affected

  • Employee session hijacking
  • Internal data exposure via staff browser
  • Trust/credibility damage if abused
  • Potential admin account takeover

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

No EPSS score yet. New CVEs are usually scored within a few days.

Lifecycle

4 events over 0 days, from the signal feeds we watch.

  1. Publishedweakness classified, att&ck mapped, record updated

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Scored 6.1 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality LowSome restricted information is disclosed, but limited in scope
  • Integrity LowData modification is possible but limited in scope or consequence
  • Availability NoneNo availability impact

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Erpnext, not every advisory.