CVE-2025-47026
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 that persists in the system and executes when other users view pages containing the affected fields.
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 versionAccess the AEM system information page at /system/console/status-productinfo or check the version from the AEM welcome page under 'Version' in the 'Information' section. Compare against the affected version ranges: < 6.5.23.0 or < 2025.5.0.Affected if The installed AEM version is less than 6.5.23.0 or less than 2025.5.0, placing it within the vulnerable range.
-
Identify form field usage in AEMReview AEM pages that contain form components such as Adaptive Forms, Core Form components, or custom form implementations. Check the CRX/DE repository at /apps or /content for nodes containing form-related components (look for 'form', 'field', 'input' node types).Affected if The AEM instance uses any form components (Adaptive Forms, Core Components forms, or custom form fields) to collect user input.
-
Inspect stored form data for malicious scriptsQuery the JCR (Java Content Repository) for suspicious script content in form field nodes. Use CRXDE Lite or the Query tool to search for patterns like '<script', 'javascript:', 'onerror=', 'onload=' within form data nodes under /content or the form's data store.Affected if Any form field data contains encoded or unencoded JavaScript code, indicating a potential XSS payload was injected and persisted.
-
Review recent form submission logsCheck AEM access logs and form-specific logs for unusual patterns in form submissions, particularly from low-privilege users submitting content that includes HTML or script tags.Affected if Logs show form submissions containing script tags or JavaScript event handlers from users with low-level permissions.
-
Audit user permissions on form-enabled pagesUse the AEM User Administration console (/security/users.html or /security/groups.html) to identify which users and groups have access to create or edit form content on affected pages.Affected if Low-privilege users (without admin or content-author permissions) have the ability to create or modify form content that could be exploited.
You are affected if your AEM version is below 6.5.23.0 or below 2025.5.0 AND you have form fields enabled that accept user input, especially if low-privilege users can submit content to those forms.
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 version 6.5.23 or later to apply the vendor patch. Alternatively, implement input validation and output encoding on form fields as a compensating control.
AEM 6.5.23.0 or later, or AEM 2025.5.0 or later
- 1. Back up your current Adobe Experience Manager instance and database before proceeding with any upgrade.
- 2. Review the Adobe Experience Manager 6.5.23.0 or 2025.5.0 release notes for upgrade requirements and prerequisites.
- 3. Ensure your system meets the minimum requirements for the target version (6.5.23.0 or 2025.5.0).
- 4. Stop the AEM instance and any related services.
- 5. Run the upgrade following Adobe's standard upgrade documentation for your deployment type.
- 6. After upgrade, verify that the stored XSS vulnerability is remediated by testing the affected form fields.
- 7. Re-enable the AEM instance and monitor for any issues.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47026 — 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-47026 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