CVE-2026-47966
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 (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 vulnerable form fields. When victims browse to pages containing the affected fields, the injected scripts execute in their browsers.
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 AEM versionNavigate to the AEM Welcome page or check the product version through the system console (/system/console/system). Compare the installed version against the affected ranges: versions before 6.5.25.0, before 2026.5.0, or equal to 6.5 (including LTS SP1 and 2026.04).Affected if The installed version is 6.5.24 or earlier, or 2026.04 or earlier, or shows version 6.5.x.
-
Identify active form fields in the environmentReview the AEM Forms or Core Components configuration to locate form-based content. Check content pages that contain Adaptive Forms, Core Form Components, or custom form field implementations.Affected if Form fields are present and accessible to low-privileged users in the system.
-
Inspect stored form data for malicious payloadsQuery the JCR (Java Content Repository) or use CRX/DE Lite to search form field content nodes under /content for suspicious script tags, event handlers (onerror, onload, onclick), or encoded JavaScript patterns in form field values.Affected if Form field data contains unsanitized script tags or JavaScript event handlers that could execute in other users' browsers.
-
Audit low-privileged user permissions and activityReview user group memberships and permissions in the AEM User Management console. Check access logs and audit logs for low-privileged users creating or modifying form field content with unusual character sequences.Affected if Low-privileged authenticated users have write access to form fields and have created or modified content containing special characters or script elements.
You are affected if your AEM version is 6.5.24 or earlier, 2026.04 or earlier, or any 6.5.x variant, and your system stores user-submitted content in form fields that is rendered without sanitization.
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 version 6.5.24 or later, LTS SP1, or 2026.04 and later to receive the security patch. Alternatively, apply Adobe's provided security hotfix for affected versions.
Adobe Experience Manager 6.5.25.0 (LTS) or 2026.5.0 (on-premise)
- Review the Adobe Experience Manager 6.5.25.0 or 2026.5.0 release notes for changes and known issues
- Create a full backup of the current AEM instance including the repository, database, and configurations
- Test the upgrade in a staging environment before applying to production
- Download Adobe Experience Manager 6.5.25.0 (for 6.5 LTS customers) or 2026.5.0 (for on-premise customers) from the Adobe distribution portal
- Install the service pack using the AEM Service Pack installation process (stop the instance, run the service pack installer, restart)
- Verify the installation by checking the AEM version in /system/console/bundles or the About Adobe Experience Manager page
- Validate that all custom code and third-party integrations function correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47966 — 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-47966 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