CVE-2025-47115
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 confidenceStored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.22 and earlier allows low-privileged attackers to inject malicious JavaScript into form fields. The payload persists in the application and executes when victims browse to pages containing the compromised fields.
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.
-
Check installed AEM versionAccess the AEM welcome page at /aem/start.html or use the system information console at /system/console/bundles to retrieve the exact version numberAffected if The installed version is earlier than 6.5.23.0 or earlier than 2025.5.0
-
Identify form fields accepting user inputReview AEM forms, adaptive forms, or custom form components in the content repository under /content or /apps that accept user submissionsAffected if Forms exist that allow unauthenticated or low-privileged users to submit data to input fields
-
Verify low-privilege user access to formsCheck group permissions for standard users or contributors who have access to form submission functionalityAffected if Low-privileged users (such as members of the contributors or users group) can access and submit form data
-
Inspect form field data for malicious scriptsQuery the repository using CRXDE Lite or a repository browsing tool to examine stored form data in /content for suspicious script tags or event handlersAffected if Stored form data contains unsanitized JavaScript, script tags, or HTML event attributes like onload, onerror, or onmouseover
-
Test CSP header configurationUse browser developer tools or curl to inspect HTTP response headers on AEM form pages for Content-Security-Policy directivesAffected if Content-Security-Policy headers are missing or configured without strict form-field restrictions
Your environment is affected if the AEM version is below 6.5.23.0 or below 2025.5.0 AND low-privileged users can submit data to form fields without proper 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.23.02025.5.0
Update Adobe Experience Manager to version 6.5.23 or later to obtain the security patch; alternatively, implement input validation/sanitization on vulnerable form fields and apply Content Security Policy headers.
6.5.23.0 (for 6.5.x branches) or 2025.5.0 (for 2024.x branches)
- Upgrade Adobe Experience Manager 6.5.x to version 6.5.23.0 or later
- If running a 2024.x version, upgrade to 2025.5.0 or later
- After upgrade, verify the XSS vulnerability is remediated by testing the affected form fields
- Consult Adobe Experience Manager release notes for any additional migration or configuration steps required post-upgrade
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-47115 — 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-47115 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