CVE-2026-47978
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 confidenceAdobe Experience Manager versions 6.5.24 and earlier contain a stored (persistent) Cross-Site Scripting vulnerability where low-privileged attackers can inject malicious JavaScript into form fields. The malicious payload persists on the server and executes in victims' browsers when they view pages containing the compromised fields. The scope change indicates the vulnerability impacts resources beyond the vulnerable component itself.
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 versionAccess the AEM system information page (typically at /system/console/config or check the 'About Adobe Experience Manager' section in the AEM welcome page) to retrieve the exact version number installed in your environmentAffected if The installed version is less than 6.5.25.0, less than 2026.5.0, or exactly 6.5 (indicating an unpatched LTS release)
-
Confirm Forms module is in useReview your AEM instance to determine if Adaptive Forms, Core Components with form functionality, or custom form-based workflows are actively configured and deployedAffected if Forms functionality is enabled and accessible to users, as the vulnerability exploits form field injection points
-
Audit low-privilege user access to formsCheck user group permissions in AEM through the User Management console (/libs/granite/security/content/useradmin) to verify if users with limited privileges (such as content-authors or default contributors) can create or edit form contentAffected if Low-privilege users have write access to form fields or form-based content assets
-
Inspect form field content for malicious scriptsQuery the repository (using CRXDE Lite at /crx/de or AEM query builder) for stored form content, examining text input fields, text areas, and form submission data for suspicious patterns such as <script>, javascript:, onerror=, or other HTML/JS injection vectorsAffected if Any stored form fields contain unsanitized script tags or event handler attributes that could execute in victim browsers
Your environment is likely affected if you run an unpatched AEM version (below 6.5.25.0 or below 2026.5.0) with active form functionality accessible to low-privilege users.
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
Implement context-aware output encoding and input validation/sanitization for all form fields handling user-supplied content. Deploy Content Security Policy (CSP) headers as defense-in-depth to mitigate XSS execution.
AEM 6.5.25.0 or later (6.5.x line); AEM 2026.5.0 or later (2026.x line)
- 1. Review the Adobe Experience Manager release notes for version 6.5.25.0 to understand changes and any migration requirements
- 2. Ensure you have a complete backup of your AEM instance and content repository
- 3. Test the upgrade in a non-production environment first
- 4. If using AEM 6.5.x, upgrade to version 6.5.25.0 or later
- 5. If using the 2026.x release train, upgrade to version 2026.5.0 or later
- 6. After upgrade, verify that the stored XSS vulnerability is resolved by testing the affected form fields
- 7. Deploy the validated upgrade to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47978 — 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-47978 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