CVE-2026-47945
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 confidenceA stored Cross-Site Scripting vulnerability exists in Adobe Experience Manager versions 6.5.24, LTS SP1, 2026.04 and earlier. Low-privileged authenticated users can inject malicious JavaScript payloads into form fields. When other users browse to pages containing these compromised fields, the malicious script executes in their browsers, enabling session hijacking, credential theft, or defacement. The scope change indicates the vulnerability can impact components outside the vulnerable form itself.
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 the installed AEM versionNavigate to the AEM System Information console (via /system/console/configMgr or check the 'About Adobe Experience Manager' page in the Tools section), or run: curl -s http://localhost:4502/system/console/bundles.json (authenticated). Look for the version string in the response.Affected if The installed version is < 6.5.25.0, < 2026.5.0, or exactly 6.5 (for example, 6.5.0 through 6.5.24.x, or any 2026.x release before 2026.5.0).
-
Determine if Forms or user-generated content modules are in useReview the AEM instance for enabled form components. Check /libs/foundation/components/form or custom form implementations under /apps. Look for Content Fragments or user-generated content models in the Assets console.Affected if Form components, Content Fragments, or any user-editable content fields are present and accessible to authenticated users.
-
Audit user accounts and their permission levelsGo to the User Administration console (Tools > Security > Users or /security/users.html). Review which users have only 'content-author' or similar low-privilege roles versus administrative roles.Affected if There are authenticated users with low-privilege accounts (non-admin) who have write access to forms or content fields.
-
Search content repository for injected script tagsUse AEM Query Builder or CRX/DE Lite (navigate to /content or relevant form submission paths) to search for entries containing '<script', 'javascript:', or 'onerror=' patterns in text fields. Run a Query Builder query: path=/content, type=nt:unstructured, property=jcr:content/*, property.value=%3Cscript%25.Affected if Any stored form submissions, content fragments, or user-editable fields contain suspicious script tags or event handlers.
-
Review recent audit logs for XSS injection attemptsAccess the AEM audit log (via Tools > Operations > Audit or directly in the repository under /var/audit), filtering for recent entries involving form submission endpoints. Look for patterns like '<script' in the audit entries.Affected if There are recent audit log entries showing low-privilege users submitting content with script tags in form fields.
You are affected if your AEM version falls within the affected ranges AND your instance has form components or user-editable content fields accessible to authenticated low-privilege users, particularly if suspicious script tags are found stored in the content repository.
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
Update to the latest Adobe Experience Manager version or apply the vendor-provided security patch. Additionally, implement output encoding and input validation on all form fields to prevent XSS execution.
AEM 6.5.25.0 or later / AEM 2026.5.0 or later
- 1. Back up your current AEM instance including the repository, database, and configuration files.
- 2. Review the Adobe Experience Manager release notes for version 6.5.25.0 or 2026.5.0 to understand any migration requirements or breaking changes.
- 3. Download the fixed version (6.5.25.0 or later / 2026.5.0 or later) from the Adobe distribution portal or Software Distribution.
- 4. Stop the current AEM instance.
- 5. Install the upgraded AEM package following Adobe's standard upgrade documentation.
- 6. Validate that all custom code, workflows, and integrations function correctly post-upgrade.
- 7. Test that the XSS vulnerability is remediated by attempting to inject scripts into the previously vulnerable form fields.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47945 — 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-47945 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