CVE-2026-47980
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAdobe Experience Manager versions 6.5.24, LTS SP1, 2026.04 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by a low-privileged attacker to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed in a victim's browser when they browse to the page containing the vulnerable field. Scope is changed.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA stored Cross-Site Scripting vulnerability in Adobe Experience Manager allows low-privileged users to inject malicious JavaScript into form fields. The malicious script persists on the affected page and executes in the browsers of users who view it, leading to potential session hijacking or data theft.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 6.5.25.0< 2026.5.0= 6.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed AEM versionLocate the AEM version via the product's version information interface, package manager, or system properties. Common methods include checking the 'Manifest.mf' file in the crx-quickstart directory, using the VersionInfo API, or accessing the 'system/console/bundles' admin console.Affected if The installed version is less than 6.5.25.0, less than 2026.5.0, or exactly 6.5.
-
Locate form field implementationsReview the application code and templates that define form input fields. Check content structures, dialog configurations (XML or JSON under /apps or /libs), and custom component implementations that render HTML form elements.Affected if Form fields exist that accept user input without proper output encoding.
-
Audit form field input validationExamine the server-side validation logic or the input handling code for form fields. Look for the presence of input sanitization, validation rules, or output encoding applied before rendering user-supplied data in HTML context.Affected if No input validation or output encoding is implemented on form field data before storage or display.
-
Verify low-privileged user access to form fieldsTest or review permissions configuration to confirm whether users with low privileges (such as standard authors or contributors with limited rights) can create or edit form field content.Affected if Low-privileged users can submit or modify values in vulnerable form fields.
A user is affected if their AEM installation matches the vulnerable version range AND form fields exist that accept user input without sanitization and are accessible to low-privileged attackers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped6.5.25.02026.5.0
Update Adobe Experience Manager to the patched version (refer to Adobe security bulletin for specific version). Implement input validation/sanitization on all form fields and configure Content Security Policy (CSP) headers to mitigate XSS execution.
AEM 6.5.25.0 or later (LTS); AEM 2026.5.0 or later (2026 release line)
- Upgrade Adobe Experience Manager 6.5.x installations to version 6.5.25.0 or later
- Upgrade Adobe Experience Manager 2026.x installations to version 2026.5.0 or later
- After upgrading, verify that the stored XSS vulnerability is remediated by testing the form fields that were previously vulnerable
- Ensure the upgrade is tested in a non-production environment before deploying to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47980 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-47980 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data