CVE-2025-46991
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 into form fields. When other users browse to pages containing these compromised fields, the injected scripts execute 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.
-
Locate the Adobe Experience Manager installationCheck your system for AEM instances - typically found in /opt/aem, /usr/local/aem, or custom installation directories. Look for the crx-quickstart folder which contains the AEM instance.Affected if No AEM installation is found on the system.
-
Determine the installed AEM versionAccess the AEM Welcome page and navigate to Help > About Adobe Experience Manager, or append /system/console/product to the AEM URL (e.g., http://localhost:4502/system/console/product). The version will be displayed in the Product Information section.Affected if The displayed version is 6.5.22 or earlier, or falls below 2025.5.0.
-
Identify custom form field components that render user inputReview your AEM instance for custom form components or adaptive forms that accept and display user-supplied content. Check the CRXDE Lite at /apps for custom components with form field implementations (look in /apps for components containing form field rendering logic).Affected if Custom form components exist that render user-supplied content without proper output encoding.
-
Inspect stored form data for potential XSS payloadsUsing CRXDE Lite or the Query Debugger, query the repository for form submission data (typically under /content/forms/af or custom form paths) and inspect the stored values for suspicious patterns like <script>, javascript:, or event handlers such as onerror, onload.Affected if Form data contains encoded or raw JavaScript vectors in form field values.
Your AEM instance is affected if it runs version 6.5.22 or earlier, or any version below 2025.5.0, and you have custom form components that render user-supplied content without 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; alternatively, implement strict input validation and output encoding on all form fields, particularly those that render user-supplied content.
AEM 6.5.23.0 or later, or AEM 2025.5.0 or later
- 1. Back up your current Adobe Experience Manager instance and verify backups are restorable
- 2. Schedule a maintenance window for the upgrade
- 3. Upgrade Adobe Experience Manager to version 6.5.23.0 or later, OR upgrade to 2025.5.0 or later
- 4. After upgrade, verify that form field inputs properly sanitize user-supplied content
- 5. Test that the XSS vulnerability is remediated by attempting to inject a benign script in form fields and confirming it is not executed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46991 — 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-46991 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