CVE-2025-46843
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 users can inject malicious JavaScript into form fields. The payload persists in the system and executes when other users view the affected page in their browsers.
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 your Adobe Experience Manager versionLog in to AEM as administrator and navigate to the Welcome page (system/console), or check the crx-quickstart folder for the version.properties file. The version is typically displayed in the 'About Adobe Experience Manager' section under Tools > Operations.Affected if The installed version is lower than 6.5.23.0 or lower than 2025.5.0.
-
Identify form components accessible to low-privileged usersReview your Content Fragment models, Adaptive Forms, or custom form components. Check user group permissions to determine which user roles (such as 'content-author' or 'community-member') have write access to form fields in content pages.Affected if Low-privileged users (non-admin) have write access to form fields that accept user-supplied content.
-
Search for stored script payloads in the content repositoryUse the AEM Query Builder or CRXDE Lite (search under /content) to query for nodes containing suspicious patterns. Look for entries containing '<script', 'javascript:', 'onerror=', 'onload=', or other HTML event handlers in text fields.Affected if Any stored content contains unencoded script tags or JavaScript event handlers.
-
Inspect form field storage and renderingExamine the data stored in the JCR (Java Content Repository) for form submission nodes. Check the HTL/Sightly templates that render these form fields to verify if output encoding is applied (look for context='unsafe' or missing encoding).Affected if Form data is stored without sanitization and rendered without proper output encoding.
-
Verify if custom input validation is implemented for formsReview the validation logic in your form components or the OSGi configuration for Input Validator services. Check whether server-side validation explicitly rejects or sanitizes HTML/script content in form fields.Affected if No server-side input validation or sanitization exists for the affected form fields.
Your environment is affected if you run AEM version 6.5.22 or earlier (or pre-2025.5.0) AND low-privileged users can submit form content that is stored and rendered without sanitization or 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
Implement proper input validation and output encoding for all form fields, particularly ensuring user-supplied content is sanitized before storage and before rendering. Consider adding Content-Security-Policy headers as defense-in-depth.
AEM 6.5.23.0 (for 6.5.x line) or 2025.5.0 (for cloud/2025 line)
- 1. Back up your Adobe Experience Manager instance, including the repository, database, and configuration files.
- 2. Review the official Adobe Experience Manager upgrade documentation for your current version at helpx.adobe.com.
- 3. If running AEM 6.5.x, upgrade to version 6.5.23.0 or later. If running the cloud/2024.x line, upgrade to version 2025.5.0 or later.
- 4. After upgrading, verify that all custom code, workflows, and integrations are functioning correctly.
- 5. Test that the stored XSS vulnerability in form fields has been remediated by attempting to inject malicious script payloads into vulnerable form fields and confirming they are properly sanitized or encoded.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46843 — 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-46843 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