CVE-2026-47939
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 · moderate confidenceStored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager allows low-privileged users to inject malicious JavaScript into form fields. When other users view pages containing these compromised fields, the script executes in their browsers, potentially leading to session hijacking or data theft.
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 versionAccess the AEM System Information console at /system/console/systeminfo or check the version.properties file in the crx-quickstart folder. Compare the version number against the affected ranges: versions below 6.5.25.0, versions below 2026.5.0, or exact version 6.5.Affected if Installed version is 6.5.x where x is less than 25, or 2026.x where x is less than 5, or exactly 6.5
-
Determine if AEM Forms are in useNavigate to the AEM Forms console at /aem/forms or check the repository under /content for form content fragments or custom form components. Inspect whether adaptive forms or foundation forms are deployed.Affected if AEM Forms or custom form components are actively deployed and accessible to users
-
Verify low-privilege user access to formsReview user group permissions in AEM at /security or via the User Management console. Check if users with low-level permissions such as 'forms-user' or 'content-author' have access to create or edit form fields.Affected if Authenticated users with limited privileges can access form creation or editing interfaces
-
Inspect stored form data for XSS payloadsQuery the JCR repository under /content/dam/forms or form submission nodes for any stored values containing script tags, javascript: URIs, or HTML event handlers (onclick, onerror, etc.). Use CRXDE Lite or a repository query to search for suspicious patterns.Affected if Form submission nodes contain unsanitized script tags or event handler attributes that could execute in browsers
The environment is affected if the AEM version falls within the vulnerable range (6.5.x below 25, 2026.x below 5, or exactly 6.5) AND forms with user-editable fields are accessible to authenticated 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
Upgrade Adobe Experience Manager to a version beyond 6.5.24, LTS SP1, or 2026.04. Additionally, implement input validation and output encoding on form fields to prevent script injection.
6.5.25.0 (for AEM 6.5 LTS) or 2026.5.0 (for quarterly release)
- Backup the current Adobe Experience Manager instance and content repository before proceeding with any upgrade
- Review Adobe's official upgrade documentation for AEM 6.5.25 or 2026.5.0 release at helpx.adobe.com
- Ensure the target environment meets the minimum system requirements for the fixed version
- Schedule a maintenance window as AEM upgrades typically require downtime
- Stop the AEM instance and any related services
- Install the fixed version (6.5.25.0 for LTS track or 2026.5.0 for quarterly track) following Adobe's standard upgrade procedure
- After upgrade, verify that the XSS vulnerability is remediated by testing form fields that were previously vulnerable
- Confirm that custom code and configurations remain functional after the 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-47939 — 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-47939 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