CVE-2025-47117
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.22 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.
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 confidenceAdobe Experience Manager versions 6.5.22 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability in form fields. A low-privileged attacker can inject malicious JavaScript payloads into vulnerable form inputs, which are stored in the system. When other users browse to pages containing these compromised form fields, the malicious 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.23.0< 2025.5.0CVSS 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.
-
Determine your AEM versionAccess the AEM system information page at /system/console/status-productinfo or check the version.properties file in the crx-quickstart folderAffected if The displayed version is earlier than 6.5.23.0 or earlier than 2025.5.0
-
Identify custom form field implementationsReview the implementation of any custom form components or adaptive forms in your AEM instance, particularly those storing user inputAffected if Custom form components that accept and store user input are present without proper input validation
-
Examine form data storage locationsQuery the AEM repository (via CRXDE Lite or repository explorer) under /content or /var for form submissions that may contain unsanitized user inputAffected if Stored form field data exists in the repository without encoded output
-
Review recent form submission logsCheck AEM error logs and form submission audit logs for any unusual script tags or JavaScript syntax in form field valuesAffected if Logs contain patterns like <script>, javascript:, or event handlers in form field values
Your AEM instance is affected if it runs version 6.5.22 or earlier, or version 2025.4 or earlier, and uses custom form fields that store user input without 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.23.02025.5.0
Apply the appropriate AEM security patch or upgrade to a version newer than 6.5.22. Additionally, implement input validation and output encoding for all form fields to prevent XSS attacks.
AEM 6.5.23.0 (for 6.5.x releases) or AEM 2025.5.0 (for cloud/continuous releases)
- 1. Review Adobe Experience Manager release notes and upgrade documentation for version 6.5.23.0 or 2025.5.0
- 2. Create a full backup of the current AEM instance including repository, database, and configuration
- 3. Test the upgrade in a non-production environment first
- 4. Execute the upgrade to AEM 6.5.23.0 (for 6.5.x line) or AEM 2025.5.0 (for cloud/continuous release line)
- 5. Verify that all custom code, workflows, and integrations function correctly post-upgrade
- 6. Confirm the XSS vulnerability is resolved by testing the previously vulnerable form fields
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47117 — 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-2025-47117 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