CVE-2025-47005
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. A low-privileged attacker can inject malicious JavaScript into form fields, which persists in the system. When other users view pages containing these compromised fields, the injected script executes in their browsers, enabling session hijacking, credential theft, or defacement.
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 Adobe Experience Manager versionLocate the AEM version number by accessing the AEM welcome page, checking the system console (Help > About Adobe Experience Manager), or examining the core JAR file name in the installation directory. Compare this version to the affected ranges: below 6.5.23.0 or below 2025.5.0.Affected if The installed version is 6.5.22 or earlier, or falls below 6.5.23.0 or 2025.5.0 respectively.
-
Confirm the presence of AEM Forms or form-based componentsReview the AEM instance for any active form components, Adaptive Forms, or form-based workflows. Check the AEM Forms UI (if enabled) or inspect the /libs or /apps directories for form-related content packages and configurations.Affected if Forms or form-based functionality is enabled and accessible to users.
-
Verify if low-privileged users have access to form authoringReview user group permissions and ACL configurations to determine whether standard or low-privileged users can create, edit, or submit content through form fields. Check group memberships and content author roles.Affected if Low-privileged or standard users have the ability to input or modify content in form fields.
-
Inspect form field content for suspicious scriptsExamine form submission data and stored content in the AEM repository (typically under /content or /etc) for any unexpected script tags, JavaScript event handlers, or encoded payloads that may indicate prior exploitation.Affected if Malicious JavaScript code is found persisted in form field data within the repository.
The environment is affected if the AEM version is below 6.5.23.0 or 2025.5.0 AND the instance has form fields accessible to low-privileged users, regardless of whether compromise is detected.
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 as provided by Adobe's official security bulletin. Additionally, implement output encoding and input validation on form fields as a defense-in-depth measure until the patch is applied.
Adobe Experience Manager 6.5.23.0 or 2025.5.0 (or later)
- Identify your current Adobe Experience Manager version to confirm it is affected (check < 6.5.23.0 or < 2025.5.0)
- Review the Adobe Experience Manager 6.5.23.0 or 2025.5.0 release notes for upgrade prerequisites and known issues
- Ensure you have a complete backup of your AEM instance including the repository, database, and configurations
- Download Adobe Experience Manager 6.5.23.0 or the 2025.5.0 release from the official Adobe distribution portal (helpx.adobe.com)
- Stop the current AEM instance and any related services
- Follow Adobe's documented upgrade procedure for your deployment type (single server or cluster)
- After upgrading, validate that all custom applications and integrations function correctly
- Verify the XSS vulnerability is resolved by testing the previously vulnerable form fields
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.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 $7,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47005 — 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-47005 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