CVE-2025-47080
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 6.5.22 and earlier contains a stored Cross-Site Scripting (XSS) vulnerability in form fields. A low-privileged authenticated attacker can inject malicious JavaScript payloads into vulnerable form inputs, which persist on the page and execute in the browsers of users who 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.
-
Check installed AEM versionLocate the AEM version number in the product welcome page, about Adobe Experience Manager section, or via the system console /system/console/systeminfo endpoint. Compare against the affected ranges: < 6.5.23.0 or < 2025.5.0.Affected if The installed version is 6.5.22.0 or earlier, or falls between 6.5.22.0 and 6.5.23.0, or is a 2025.x version prior to 2025.5.0.
-
Identify active form componentsReview the AEM instance for deployed form components (such as Adaptive Forms, Core Form components, or custom form containers) that accept and store user-submitted data in the repository.Affected if Form components that persist user input are actively deployed and accessible to low-privileged users.
-
Audit form field input handlingInspect the form component configuration and any associated validation or sanitization logic in the HTML/HTL templates or Sling models to determine if input is being properly escaped before storage.Affected if Form fields lack proper output encoding or input validation, allowing raw user input to be stored and rendered.
-
Search for suspicious content in repositoryUse the AEM Query Builder or CRX/DE to search repository nodes under /content for any unexpected script tags, javascript: URIs, or event handler attributes in form-related content nodes.Affected if Malicious script payloads are found stored in form-related content nodes in the repository.
The environment is affected if the AEM version is below 6.5.23.0 (or below 2025.5.0 for the 2025 release line) AND form components that accept user input are in use without proper sanitization, allowing stored XSS execution.
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
Upgrade Adobe Experience Manager to version 6.5.23 or later to receive the security patch. As a compensating control, implement strict input validation on form fields and configure Content-Security-Policy headers to mitigate XSS execution.
AEM 6.5.23.0 or later, or AEM 2025.5.0 or later
- Identify the current Adobe Experience Manager version in use
- Review Adobe's official release notes for the fixed versions (6.5.23.0 or 2025.5.0) to understand the complete list of security fixes
- Plan and schedule the upgrade following Adobe's official upgrade documentation
- Perform a complete backup of the current AEM instance and content repository
- Test the upgrade in a non-production/staging environment first
- Apply the upgrade to production environments after successful testing
- Verify the upgrade was successful and validate that the XSS vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47080 — 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-47080 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