CVE-2026-47975
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 confidenceStored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager allows low-privileged attackers to inject malicious JavaScript into form fields. The payload persists in the application and executes in victim browsers when viewing the affected page. Scope is changed, indicating impact extends 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.
-
Verify Adobe Experience Manager versionAccess the AEM Welcome page or use the system console (/system/console/status-productinfo) to confirm the installed AEM version. Compare against affected ranges: < 6.5.25.0, < 2026.5.0, or exactly version 6.5.Affected if The installed version is 6.5.x where x is less than 25, or the version is listed as exactly 6.5, or the version is below 2026.5.0.
-
Identify accessible form componentsReview all AEM form components (Adaptive Forms, Core Components form fields, or custom form implementations) that accept user input and are accessible to users with standard or contributor-level permissions.Affected if Low-privileged users (non-admin) can access and submit data to form components without additional security review.
-
Inspect custom form component implementationsLocate any custom form components in /apps or /libs that handle user input. Examine the JSP, HTL, or Java code for these components to determine if they perform input validation and output encoding on user-supplied data.Affected if Custom form components exist and lack proper input validation or output encoding on field values before rendering.
-
Review Content Security Policy configurationCheck the Apache Sling Content Distribution or dispatcher configuration for Content-Security-Policy headers. Also verify OSGi configuration for the CSRF Filter and CSP Manager.Affected if Content Security Policy headers are not configured, or CSP headers allow unsafe-inline scripts, providing no defense-in-depth against XSS execution.
-
Audit existing form submissions for potential malicious payloadsQuery the AEM repository (via CRXDE Lite or search) for stored form data in /content or /var that may contain script tags, javascript: URIs, or event handlers in text fields.Affected if Form submission nodes contain unsanitized HTML, script tags, or JavaScript event handlers in field values.
A user is affected if their AEM version falls within the vulnerable range AND they have form components accessible to low-privileged users without proper input validation, output encoding, or CSP headers in place.
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 AEM to a patched version beyond 6.5.24/LTS SP1/2026.04. Implement output encoding for form fields and deploy Content Security Policy headers to mitigate XSS execution.
Adobe Experience Manager 6.5.25.0 (LTS) or 2026.5.0 and later
- Backup your current Adobe Experience Manager instance and all content repositories before proceeding
- Review the Adobe Experience Manager 6.5.25.0 (LTS) or 2026.5.0 release notes for any compatibility considerations and changes
- Test the upgrade in a non-production/staging environment to verify compatibility with custom code and configurations
- Upgrade the AEM instance to version 6.5.25.0 or later (for LTS track), or to 2026.5.0 or later (for the newer release track)
- Verify the upgrade was successful and test that the stored XSS vulnerability is no longer exploitable in the affected form fields
- Deploy the validated upgrade to production following standard AEM deployment procedures
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47975 — 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-47975 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