CVE-2026-47953
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 versions 6.5.24, LTS SP1, 2026.04 and earlier allows low-privileged attackers to inject malicious JavaScript into form fields. The malicious payload persists in the system and executes in victims' browsers when they view pages containing the affected fields. The CVSS 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.
-
Check Adobe Experience Manager versionNavigate to the AEM Welcome page or access the system information via the Operations dashboard. The version is typically displayed on the AEM Start page or can be retrieved via the /system/console/info endpoint. Compare the installed version against the affected ranges: < 6.5.25.0, < 2026.5.0, or 6.5.xAffected if The installed version is 6.5.24, LTS SP1, 2026.04, or any earlier version within the 6.5.x or 2026.x release lines
-
Identify enabled form authoring featuresReview the AEM Forms configuration and the AEM Forms App settings. Check if Forms functionality is enabled and accessible to low-privileged users (such as those with content-author or user-level permissions). Inspect the form models and adaptive forms configurations in the CRX/DE repository under /content/formsAffected if Forms or adaptive forms are enabled and accessible to users with low-privileged accounts (non-admin users)
-
Inspect form field definitions for malicious contentAccess the CRX/DE repository and navigate to form container definitions under /content/forms/af or /libs/fd/af. Review the XML or JSON configuration of form fields, particularly labels, placeholders, and default values, for any suspicious script tags, event handlers (onclick, onerror, etc.), or encoded JavaScript payloadsAffected if Any form field definition contains <script> tags, javascript: URIs, or event handler attributes containing script code
-
Review form submission data for injected scriptsCheck the AEM Forms workflow inbox or the data store where form submissions are stored. Inspect submitted form data in the repository under /content/forms/submissions or within AEM Forms workflow instances. Look for XSS payloads in text fields such as <script>, <img src=x onerror=>, javascript:, or other script injection patternsAffected if Form submission records contain unencoded script tags or event handlers that would execute when rendered
You are affected if your AEM version is 6.5.24 or earlier in the 6.5.x line, 2026.04 or earlier in the 2026.x line, and your environment allows low-privileged users to author or submit form content that is rendered without proper output encoding.
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 vendor-provided patches for the affected AEM versions. Implement input validation and output encoding for all form fields, and review AEM's Cross-Site Scripting Protection settings.
Adobe Experience Manager 6.5.25.0 (LTS) or AEM 2026.5.0
- Identify your current Adobe Experience Manager version by checking the AEM console or system information
- If running AEM 6.5.x LTS, upgrade to version 6.5.25.0 or later
- If running AEM 2026.x, upgrade to version 2026.5.0 or later
- After upgrade, verify the form fields mentioned in the security bulletin no longer allow script injection
- Test that the XSS vulnerability is no longer exploitable in affected form fields
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47953 — 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-47953 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