CVE-2026-47981
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 Cross-Site Scripting (XSS) vulnerability in form fields. A low-privileged authenticated attacker can inject malicious JavaScript payloads into vulnerable form input fields. When legitimate users subsequently browse to pages containing these compromised fields, the injected scripts execute in their browsers, potentially enabling session hijacking, credential theft, or unauthorized actions. The scope change indicates the vulnerability impacts resources beyond the affected component.
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 AEM versionNavigate to the AEM System Information console (http://<host>:<port>/system/console/status-productinfo) or check the CRX Explorer properties for the version string. Look for aem-version or productVersion properties.Affected if Version is 6.5.x where x is 24 or lower, or version equals 6.5, or version is below 2026.5.0 (such as 2024.x or 2025.x releases).
-
Verify Forms or Adaptive Forms module is in useCheck if the Forms add-on or Adaptive Forms feature is installed by reviewing the package manager (http://<host>:<port>/crx/packmgr) for 'aem-forms' packages, or check the Feature Console (http://<host>:<port>/libs/granum/framework/features) for Forms capability.Affected if Forms or Adaptive Forms modules are installed and enabled, as the XSS vulnerability exists in form field components.
-
Inspect form field content for injected scriptsQuery the JCR repository via CRXDE (http://<host>:<port>/crx/de) or use Query Builder to search nodes under /content/forms for any <script> tags, javascript: URLs, or common XSS payloads (such as <img src=x onerror=...> or <iframe>) stored in form field values.Affected if Malicious JavaScript or HTML injection is found stored in form field data nodes.
-
Review low-privileged user permissions on form contentNavigate to Users or Groups administration (http://<host>:<port>/security/users.html or /security/groups.html), select a low-privilege user, and verify if they have create, modify, or delete permissions on /content/forms paths or related form content nodes.Affected if Low-privileged users (without admin rights) can create, edit, or submit form content, allowing them to inject the stored XSS.
You are affected if your AEM version is 6.5.24 or earlier (or 6.5), Forms/Adaptive Forms is enabled, and low-privileged users can access or edit form fields where malicious scripts could be injected.
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
Upgrade to Adobe Experience Manager version 6.5.25 or later / 2026.05 or later. Until patched, implement strict input validation and output encoding on all form fields, and consider Content Security Policy headers to mitigate XSS execution.
Upgrade to AEM 6.5.25.0 (LTS track) or 2026.5.0 (2026 track) or later
- 1. Identify current Adobe Experience Manager version by checking the system information in the AEM console or about page
- 2. Review Adobe Experience Manager 6.5.25.0 or 2026.5.0 release notes for security fixes and any known migration requirements
- 3. Create a full backup of the current AEM instance including content repository and configuration
- 4. Test the upgrade in a non-production environment to identify any compatibility issues
- 5. Schedule a maintenance window for the production upgrade
- 6. Perform the upgrade to version 6.5.25.0 (LTS) or 2026.5.0 (2026 track) following Adobe's official upgrade documentation
- 7. After upgrade, verify the XSS vulnerability is remediated by testing the previously vulnerable form fields
- 8. Run regression tests to ensure existing functionality works as expected
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-47981 — 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-47981 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