CVE-2026-47957
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-privilege authenticated users to inject malicious JavaScript into form fields. When victims browse to pages containing the injected script, it executes in their browsers, potentially stealing session cookies or performing actions on behalf of the user.
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.
-
Confirm AEM installation and locate versionAccess the AEM System Information console at /system/console/systeminfo or the About Adobe Experience Manager page at /libs/granite/core/content/about.html. Alternatively, check the JAR file properties or version.properties in the AEM installation directory.Affected if The installed version is less than 6.5.25.0, less than 2026.5.0, or exactly equals 6.5.
-
Identify if AEM Forms or adaptive forms are enabledNavigate to the AEM Forms console at /aem/forms or check for the presence of adaptive form workflows in the workflow models console at /libs/cq/workflow/admin/console/content/models.html. Look for form-related packages in Package Manager.Affected if AEM Forms, adaptive forms, or any form-based components are installed and enabled in the AEM instance.
-
Check for low-privileged user access to form authoringNavigate to the user administration console at /useradmin and review group memberships. Look for groups like 'content-authors' or custom groups assigned form-creation permissions. Check the permission matrix at /libs/cq/security/authorizablepermissions.html.Affected if Low-privileged users (non-admin) have permissions to create, edit, or submit forms or form-based content.
-
Inspect custom form field components for input validationReview custom component XML definitions in /apps that contain form input fields (input, textarea, select). Check the JSP or HTL scripts for the presence of server-side input validation and output encoding using methods like XSS API or ESAPI.Affected if Custom form components exist and lack proper input validation or output encoding on form field submissions.
You are affected if your AEM version falls within the affected ranges and low-privileged users can author or submit form content without strict input validation and output encoding 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 to a patched version of Adobe Experience Manager. Additionally, implement input validation and output encoding for all form fields, and configure Content Security Policy headers to mitigate XSS execution.
Upgrade to AEM 6.5.25.0 or later for the 6.5 LTS line, or 2026.5.0 or later for the cloud release line
- Identify current Adobe Experience Manager version by checking the AEM welcome page or using the version manifest in crx-quickstart
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47957 — 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-47957 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