CVE-2026-47973
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 contains a stored XSS vulnerability in form fields affecting versions 6.5.24, LTS SP1, 2026.04 and earlier. A low-privilege attacker can inject malicious JavaScript that executes when other users browse to pages containing the compromised form fields. The scope change indicates the vulnerability impacts resources beyond the vulnerable 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 installed AEM versionAccess the AEM System Information console at /system/console/status or check the version.properties file in the crx-quickstart directory. Alternatively, query the version via the AEM Web Console or API endpoint.Affected if The installed version is less than 6.5.25.0, less than 2026.5.0, or exactly 6.5 without a service pack applied.
-
Verify low-privilege user access to form componentsCheck if any user group with limited permissions (such as content-authors or custom low-privilege groups) has write access to Form or Adaptive Form components in the AEM content structure under /content or /apps.Affected if Low-privilege users can create or edit form fields in AEM content pages.
-
Inspect form field configurations for missing output encodingReview the form component XML or dialog configurations in the CRX/DE Lite (accessible at /crx/de) under the relevant form component nodes. Check the properties for encodeHTML or safeHTML filters.Affected if Form fields lack proper output encoding configurations or CSP headers are not enforced on the affected pages.
-
Scan form submission data for malicious payloadsQuery the AEM repository (via CRXDE or the Query Builder API) for stored script tags or JavaScript event handlers in form-related content nodes under /content, searching for patterns like <script, javascript:, or onload/onerror attributes.Affected if Malicious JavaScript payloads are found stored in form field content nodes.
-
Review affected pages with a browser developer toolLoad pages containing user-generated form fields in a browser and inspect the HTML source via View Source or DevTools to see if user input is rendered without encoding.Affected if User-supplied form data renders as raw HTML/JavaScript in the page output.
A user is affected if their AEM version falls within the vulnerable ranges and their environment allows low-privilege users to inject and persist malicious scripts into form fields that render unencoded to other 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
Apply the vendor patch for this vulnerability and implement output encoding/sanitization for all form field inputs to prevent script injection. Review existing content for malicious scripts that may have already been injected.
Adobe Experience Manager 6.5.25.0 or later, or 2026.5.0 or later
- Back up the current AEM instance including the repository, configurations, and any custom code
- Review the Adobe Experience Manager upgrade documentation for your specific version and deployment type
- Upgrade Adobe Experience Manager to version 6.5.25.0 or later, or version 2026.5.0 or later
- After upgrade, verify that the AEM instance starts successfully and all services are operational
- Test the form fields that were previously vulnerable to confirm the XSS vulnerability is remediated
- Validate that custom workflows, integrations, and published content function correctly post-upgrade
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-47973 — 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-47973 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