CVE-2025-46974
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 where a low-privileged attacker can inject malicious JavaScript into vulnerable form fields. The malicious payload persists in the system and executes in victims' browsers when they view pages containing the affected form 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.
-
Determine installed AEM versionAccess the AEM welcome page or check the product.info via the system console. Navigate to 'Help' > 'Version' from the AEM start page, or append '/system/console/product' to your AEM base URL to view the product version information.Affected if The installed version is 6.5.22 or earlier, or falls below 2025.5.0 for the newer release cadence.
-
Identify form components in useReview your AEM instance for any Adaptive Form components, Core Form components, or custom form field components that accept user input. Check the AEM Sites console for pages containing form components under /content or /conf directories.Affected if The instance uses any form components that handle user-submitted data without server-side input validation.
-
Inspect form data in the repositoryQuery the AEM repository using CRXDE Lite (accessible at /crx/de) or the Query Builder. Search nodes under /content for form submission data, typically stored in /content/forms/af or custom form container paths. Look for any HTML or script tags within form field values.Affected if Stored form data contains unsanitized HTML, script tags, or JavaScript event handlers that were not filtered on submission.
-
Review AEM audit logs for XSS patternsAccess the AEM error log or audit log files. Search for entries containing patterns typical of XSS exploitation attempts such as '<script', 'javascript:', 'onerror=', 'onload=', or other event handlers within form-related request parameters.Affected if Audit logs show form submissions containing suspicious script injection patterns.
Your environment is affected if the installed AEM version is 6.5.22 or earlier, or below 2025.5.0, AND you have form components that accept user input in your instance.
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 patch the vulnerability. Additionally, implement input validation and output encoding on form fields, and configure Content Security Policy (CSP) headers as defense-in-depth.
AEM 6.5.23.0 or later; AEM as a Cloud Service 2025.5.0 or later
- Identify your current Adobe Experience Manager version by checking the product console or system information
- For AEM 6.5.x versions: Upgrade to AEM 6.5.23.0 or later
- For AEM as a Cloud Service: Upgrade to 2025.5.0 or later
- After upgrading, verify the XSS filter configurations are functioning correctly in the Adobe Granite XSS API console
- Test the form fields that were previously vulnerable to confirm the stored XSS vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.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-46974 — 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-46974 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