CVE-2025-46922
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 XSS vulnerability where low-privileged users can inject malicious JavaScript into form fields. The injected script persists on the page and executes in victim users' browsers when they view the affected page.
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 versionNavigate to AEM Help > About or access the system information console to retrieve the exact version number of your Adobe Experience Manager installationAffected if The version is lower than 6.5.23.0 or lower than 2025.5.0 (the 2025.5.0 release is also affected)
-
Identify form-enabled content pathsReview your AEM instance for content structures that utilize form components or custom form fields, particularly in DAM, user-generated content areas, or community featuresAffected if Form fields exist that accept user input and are accessible to low-privileged users without requiring admin permissions
-
Audit stored form data for malicious payloadsQuery your repository or use AEM grep tools to search JCR content nodes for common XSS patterns in form field values, such as script tags, event handlers (onload, onerror, onclick), or javascript: URLsAffected if Stored form data contains unsanitized script tags or event handler attributes that could execute in other users' browsers
-
Review Content Security Policy configurationCheck your dispatcher configuration or AEM HTML Library Manager settings for Content-Security-Policy headers or X-Frame-Options headers that could provide defense-in-depth against XSSAffected if No CSP headers are configured and no output encoding is applied to form field outputs
You are affected if your AEM version is below 6.5.23.0 or below 2025.5.0 AND your instance exposes form fields accessible to low-privileged users without proper output encoding.
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 to AEM version 6.5.23 or later. Additionally, implement output encoding on form fields and consider Content Security Policy headers to mitigate XSS execution.
Adobe Experience Manager 6.5.23.0 or later (6.5.x line); 2025.5.0 or later (2025/cloud line)
- Plan and schedule a maintenance window for the upgrade
- Back up the current Adobe Experience Manager instance including content and configurations
- Upgrade Adobe Experience Manager to version 6.5.23.0 or later (for 6.5.x on-premise releases)
- Alternatively, upgrade to version 2025.5.0 or later if using the cloud/2025 release line
- Test the upgrade in a non-production environment to verify compatibility with custom code and integrations
- Deploy the upgraded version to production
- Verify the XSS vulnerability is resolved by testing that malicious scripts cannot be injected into form fields
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.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 $4,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46922 — 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-46922 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