CVE-2025-46841
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 vulnerability where low-privileged authenticated users can inject malicious JavaScript payloads into form fields. The malicious script persists in the system and executes in the browsers of other users who view pages containing the compromised 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 your Adobe Experience Manager versionLocate the AEM version number in the product about page (Help > About Adobe Experience Manager) or in the crx-quickstart/README.txt file. Compare this against the affected version ranges: < 6.5.23.0 or < 2025.5.0Affected if Your installed version is below 6.5.23.0 or below 2025.5.0
-
Identify low-privileged user accessReview user permissions in AEM to determine if any authenticated users exist with limited privileges, particularly those with access to create or edit content in form componentsAffected if Low-privileged authenticated users have access to edit form fields in your AEM instance
-
Inspect form fields for persisted scriptsQuery your AEM content repository (CRXDE Lite or via Groovy script) for script tags within form component nodes under /content or /etc, looking for <script> tags or javascript: URIs in text fieldsAffected if Form field content in your repository contains unencoded script tags or malicious JavaScript payloads
-
Check recent content authored by low-privilege usersReview content modified recently by users in the authors group or other limited-privilege groups. Inspect form-based components like adaptive forms, content fragments with form fields, or custom form implementationsAffected if Low-privilege users have authored form content that contains executable script code
You are affected if your AEM version is below 6.5.23.0 or below 2025.5.0 AND low-privileged authenticated users have access to form fields where malicious scripts could be stored and executed in other users browsers.
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 obtain the security patch. Additionally, implement input validation and output encoding on all user-supplied form fields to prevent XSS.
AEM 6.5.23.0 (on-premises) or AEM as a Cloud Service 2025.5.0+
- Verify current Adobe Experience Manager version in use (AEM 6.5.x or AEM as a Cloud Service)
- For AEM 6.5.x on-premises: Plan upgrade to version 6.5.23.0 or later
- For AEM as a Cloud Service: Plan upgrade to version 2025.5.0 or later
- Review Adobe's upgrade documentation for your deployment type
- Execute upgrade following Adobe's recommended upgrade procedure
- Test the upgraded environment to confirm functionality
- Verify the XSS vulnerability is remediated by attempting to inject script in affected form fields
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.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 $5,024.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46841 — 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-46841 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