CVE-2025-46902
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 confidenceStored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.22 and earlier allows low-privileged authenticated users to inject malicious JavaScript into form fields. The injected script persists in the system and executes in victims' browsers when they view pages containing the compromised form 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.
-
Identify installed AEM versionAccess the AEM Welcome page or product info endpoint, typically at /libs/cq/core/content/welcome.html or through the system console at /system/console/product. Locate the version number displayed in the product information area.Affected if The version displayed is 6.5.22 or earlier, or falls below 2025.5.0 (such as 2024.x versions)
-
Confirm AEM release lineDetermine whether the installation is AEM 6.5 (on-prem) or AEM as a Cloud Service. Check the product info for the release identifier - 6.x indicates on-prem while Cloud Service shows a date-based version.Affected if Running any vulnerable release line (6.5.22 or earlier, or any version before 2025.5.0)
-
Identify accessible form componentsReview the AEM Forms or Editable Templates in the system. Check which form components (such as text fields, text areas, or custom form fields) are available to low-privileged users (contributors or users with content-author permissions).Affected if Low-privileged authenticated users have access to create or edit form fields in any content fragment, experience fragment, or editable template
-
Inspect form field configurationsNavigate to the form field definition in the repository (under /apps or /content depending on implementation). Examine the field's XML or sling:resourceType configuration for any custom validation or encoding settings.Affected if Form fields lack server-side input validation or output encoding is not explicitly configured on the field component
-
Check for existing XSS payloadsQuery the repository for any suspicious content in form field values. Use CRXDE Lite or the Query tool to search jcr:content nodes for script tags or JavaScript event handlers in text fields.Affected if Any form field content contains script tags, javascript: handlers, or on* event attributes that were not intentionally placed by administrators
You are affected if your AEM version is below 6.5.23.0 or below 2025.5.0, and low-privileged users can access or edit form fields without enforced 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
Apply the vendor-supplied security patch for AEM. Additionally, implement output encoding on all form field outputs and configure Content Security Policy headers to mitigate XSS execution.
AEM 6.5.x: upgrade to 6.5.23.0 or later; AEM as a Cloud Service: upgrade to 2025.5.0 or later
- Identify the current Adobe Experience Manager version in use
- For AEM 6.5.x installations: Upgrade to version 6.5.23.0 or later
- For AEM as a Cloud Service: Upgrade to version 2025.5.0 or later
- Before upgrading, perform a full backup of the AEM instance and content repository
- Test the upgrade in a non-production environment before deploying to production
- After upgrading, verify that the XSS vulnerability is resolved by testing the affected form fields
- Ensure all custom code and third-party integrations are compatible with the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.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,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46902 — 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-46902 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