CVE-2025-46992
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 · moderate confidenceAdobe Experience Manager versions 6.5.22 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability in form fields. A low-privilege attacker can inject malicious JavaScript into form input fields, which then 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 AEM product versionLocate the AEM version number in the product information or about the product page (typically at /libs/cq/core/content/info.html or via the Felix console). Compare it against the affected ranges: < 6.5.23.0 or < 2025.5.0Affected if The installed version is 6.5.22 or earlier, or falls between 6.5.23.0 and 2025.5.0 (exclusive)
-
Identify enabled form componentsReview the AEM instance for any deployed forms that accept user input, including custom form components, adaptive forms, or core form components that render input fields on published pagesAffected if Form components that accept user input are actively configured and published on the instance
-
Verify low-privilege user access to formsExamine the user permissions and group memberships configured for the forms functionality. Determine if users with low-level privileges (such as content authors, community members, or unauthenticated users) have the ability to create or modify form field contentAffected if Users with low privileges can submit or modify values in form input fields
-
Inspect form input handlingReview the form field configurations and any associated input validation or output encoding settings. Check whether form inputs are being rendered back to users without proper sanitizationAffected if Form field inputs are rendered on pages without encoding or sanitization applied to the submitted values
You are affected if your AEM version is below 6.5.23.0 (or below 2025.5.0) AND your instance has form components that accept user input accessible to low-privilege users, with unsanitized output being displayed to other users.
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
Apply the available Adobe patch for AEM to address the vulnerability, and implement output encoding/sanitization for all form field inputs to prevent script injection.
AEM 6.5.23.0 or later; AEM as a Cloud Service 2025.5.0 or later
- 1. Back up your current AEM instance including repository, database, and configurations
- 2. Review Adobe's upgrade documentation for your target version at helpx.adobe.com
- 3. Test the upgrade in a staging environment before deploying to production
- 4. Upgrade AEM 6.5.x instances to version 6.5.23.0 or later
- 5. Upgrade AEM as a Cloud Service instances to version 2025.5.0 or later
- 6. Validate that the stored XSS vulnerability is remediated by testing the previously vulnerable form fields
- 7. Deploy the upgraded instance to production after successful validation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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 $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46992 — 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-46992 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