CVE-2025-47045
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 XSS vulnerability in Adobe Experience Manager versions 6.5.22 and earlier allows low-privileged attackers to inject malicious JavaScript into form fields. The malicious payload 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.
-
Determine installed AEM versionAccess the AEM Welcome page or check the product.info via /system/console or the crx/de quickstart properties file (app.ini or quickstart.properties). Compare against 6.5.23.0 and 2025.5.0.Affected if Installed version is below 6.5.23.0 or below 2025.5.0
-
Identify exposed form componentsReview the AEM instance for any published or exposed forms that accept user input, including Adaptive Forms, Core Form components, or custom form implementations in content pages.Affected if Forms accepting user input exist and are accessible to low-privileged users
-
Inspect form field data for XSS payloadsQuery the JCR repository (via CRXDE Lite or AEM query tool) under /content for stored form submission data or examine the granite data store for form field values containing script tags, javascript:, or HTML event handlers.Affected if Form submission nodes contain unsanitized script tags or event handler attributes in field values
The environment is affected if the installed AEM version is below 6.5.23.0 or below 2025.5.0 AND forms accepting user input are exposed, particularly if stored form data contains suspicious payloads.
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 AEM 6.5.23 or later to obtain the security patch. As a compensating control, implement strict input validation and output encoding on form fields until the patch is applied.
AEM 6.5.23.0+ or AEM 2025.5.0+ (depending on which release line is in use)
- Identify the current Adobe Experience Manager version in use
- If running 6.5.x line, plan upgrade to version 6.5.23.0 or later
- If running 2025.x.x line, plan upgrade to version 2025.5.0 or later
- Schedule maintenance window for the upgrade process
- Review Adobe's official upgrade documentation for AEM 6.5.23 or the 2025.5 release
- Perform upgrade in a non-production environment first to validate compatibility
- Test critical workflows and custom integrations after upgrade
- Apply upgrade to production environment
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47045 — 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-47045 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