CVE-2025-47006
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 into these fields, which persists on the page and executes in victims' browsers when they view the affected content.
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.
-
Identify the installed AEM versionAccess the AEM system information console or check the version properties file to determine the exact version number running in your environmentAffected if The version is below 6.5.23.0 or below 2025.5.0, indicating the instance is within the affected range
-
Determine if low-privileged user access is enabledReview user permission configurations to confirm whether standard or low-privileged user accounts can access and modify form fields within AEMAffected if Low-privileged users have the ability to create or edit content containing form fields, enabling potential exploitation
-
Locate accessible form fields in the environmentAudit the AEM instance for form components that accept user input, particularly those that may not have output encoding enabledAffected if Form fields exist that store user input without proper validation or encoding, creating conditions where stored XSS could be injected and persisted
-
Inspect stored form data for suspicious contentReview database or content repository entries for form fields, looking for any unexpected script tags, JavaScript URLs, or event handler attributes that may indicate existing exploitationAffected if Malicious JavaScript payloads are found stored in form field content within the AEM 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.23.02025.5.0
Update Adobe Experience Manager to a version newer than 6.5.22. Additionally, implement input validation and output encoding on all form fields to prevent XSS injection.
AEM 6.5.23.0 (on-premise) or AEM Cloud Service 2025.5.0+
- Review the current Adobe Experience Manager version in use (check /system/console or About Adobe Experience Manager page)
- If using AEM 6.5.x, upgrade to version 6.5.23.0 or later
- If using AEM as a Cloud Service, upgrade to version 2025.5.0 or later
- Consult Adobe's official upgrade documentation at helpx.adobe.com for detailed upgrade procedures
- Test the upgrade in a staging environment before deploying to production
- Verify the XSS vulnerability is resolved by attempting to inject script content into form fields
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47006 — 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-47006 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