CVE-2025-47113
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 persist on the page. When victims browse to the affected page, the malicious script executes in their browser, potentially enabling session hijacking or credential 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.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 installed AEM versionAccess the AEM System Information console at /system/console/status-productinfo or check the version from the AEM startup log and compare against the affected ranges: 6.5.x versions below 6.5.23.0 and 2025 versions below 2025.5.0Affected if The installed version falls below 6.5.23.0 for 6.5.x releases or below 2025.5.0 for 2025 releases
-
Identify deployed Adaptive Form componentsReview the AEM content inventory or form component usage in the /apps and /content directories, looking for Adaptive Forms or Form objects that accept user inputAffected if Adaptive Form components or any custom form implementations are deployed and accessible to users
-
Verify low-privileged user access to form authoringLog in as a user with limited permissions (such as a standard content author or a guest user) and attempt to access form creation or editing interfaces at typical paths like /aem/forms or content/formsAffected if Low-privileged users can access form authoring or submission interfaces without elevated administrative rights
-
Inspect existing form data for suspicious patternsQuery the repository for stored form submissions using CRXDE Lite (accessible at /crx/de) or the Form Manager, searching the data stores for common XSS payload patterns such as <script, javascript:, onerror=, onload=, or encoded variantsAffected if Stored form data contains unsanitized script tags or event handler attributes in form field values
You are affected if your AEM version is below 6.5.23.0 or below 2025.5.0 AND you have form components accessible to low-privileged users that accept user input without proper 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
Update to Adobe Experience Manager version 6.5.23 or later. Additionally, implement input validation and output encoding on all form fields, and consider adding Content-Security-Policy headers to mitigate XSS execution.
AEM 6.5.23.0 (for 6.5.x releases) or AEM Cloud Service 2025.5.0 (for Cloud Service)
- 1. Identify the current Adobe Experience Manager version running in your environment
- 2. If running AEM 6.5.x, plan upgrade to version 6.5.23.0 or later
- 3. If running AEM as a Cloud Service, plan upgrade to version 2025.5.0 or later
- 4. Schedule maintenance window for the upgrade following Adobe's standard upgrade procedures
- 5. Test the upgrade in a non-production environment first
- 6. After upgrade, verify that the stored XSS vulnerability is remediated by testing the affected form fields
- 7. Deploy to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47113 — 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-47113 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