CVE-2025-47086
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-privilege attacker can inject malicious JavaScript payloads into vulnerable form inputs, which persist on the page and execute in victim users' 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.
-
Check the installed AEM versionNavigate to the AEM welcome page or check the version.properties file in the crx-quickstart folder. The version is typically displayed on the Welcome screen under 'Adobe Experience Manager' or can be queried via the system console (/system/console/bundles).Affected if The installed version is 6.5.22 or earlier, or falls below 6.5.23.0 or 2025.5.0 respectively.
-
Identify active form fields that accept user inputReview the AEM Form component configurations and look for any custom form implementations or Adaptive Forms that collect user input. Check the CRX/DE repository under /apps or /libs for form field components.Affected if Form fields that perform insufficient input validation are present and accessible to low-privilege users.
-
Inspect stored form data for suspicious scriptsQuery the repository (via CRXDE Lite or AEM Query Builder) for stored form submissions containing HTML script tags or JavaScript event handlers. Search nodes under /content for patterns like <script, javascript:, onerror=, onload=.Affected if Malicious JavaScript payloads are found persisted in form field data nodes.
-
Review low-privilege user access to form authoringCheck group memberships and permissions for users who have access to create or edit form content. Verify if anonymous or low-privileged users can submit forms that get stored in the repository.Affected if Low-privilege or anonymous users have write access to form-enabled content paths.
You are affected if your AEM version is below 6.5.23.0 or 2025.5.0 AND your environment contains form fields that accept user input accessible to low-privilege users.
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
Apply Adobe's security update (AEM 6.5.23 or later) to patch the XSS vulnerability. Additionally, implement input validation and output encoding on all form fields, and consider Content Security Policy headers as a defense-in-depth measure.
6.5.23.0 or later for AEM 6.5.x; 2025.5.0 or later for AEM as a Cloud Service
- 1. Identify your current Adobe Experience Manager version by checking the product information in the AEM console or system/console/about page
- 2. For AEM 6.5.x installations: Plan upgrade to version 6.5.23.0 or later
- 3. For AEM as a Cloud Service: Plan upgrade to version 2025.5.0 or later
- 4. Review the Adobe Experience Manager release notes for the target version to understand changes and requirements
- 5. Create a full backup of your current AEM instance including content, configurations, and custom code
- 6. Test the upgrade in a non-production environment first to verify compatibility with custom implementations
- 7. Execute the upgrade following Adobe's standard upgrade procedures for your deployment type
- 8. After upgrade, verify that the XSS vulnerability is remediated by testing the previously vulnerable form fields
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47086 — 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-47086 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