CVE-2025-46888
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 (XSS) vulnerability in form fields. A low-privileged attacker can inject malicious JavaScript into vulnerable form inputs that persists on the server. When other users view pages containing these compromised form fields, the malicious script executes 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.
-
Identify the installed Adobe Experience Manager versionAccess the AEM Web Console or check the version.properties file in the crx-quickstart directory. Navigate to /system/console/configMgr or append /crx/packmgr/service.jsp?cmd=version to the AEM URL.Affected if The installed version is below 6.5.23.0 (for 6.x releases) or below 2025.5.0 (for Cloud/2025 releases)
-
Verify the AEM 6.x version numberCheck the version in the AEM Welcome page footer or via the Manifest file at /libs/cq/core/content/welcome/manifest.jsonAffected if Version reads 6.5.22 or earlier
-
Verify the AEM 2025.x version numberCheck the version in the AEM About Adobe Experience Manager page (Help > About) or via the version endpointAffected if Version reads below 2025.5.0 such as 2025.4.0 or earlier
-
Confirm form field components are in useReview the AEM implementation for usage of Core Components form containers (form-text, form-hidden, form-options) or Foundation form components in published pages.Affected if Form fields that accept user input are actively used on the AEM instance
The environment is affected if the installed AEM version is 6.5.22 or earlier, or 2025.4.0 or earlier, AND the system uses form fields that could accept and persist user input.
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 Adobe Experience Manager to version 6.5.23 or later to resolve the stored XSS vulnerability in form fields.
AEM 6.5.23.0 or later; AEM as a Cloud Service 2025.5.0 or later
- Identify your current Adobe Experience Manager version by checking the Product Information in AEM System Overview or the cq.product.version property in the OSGi console
- For AEM 6.5.x users: Upgrade to version 6.5.23.0 or later by obtaining the update from Adobe Software Distribution or your licensing portal
- For AEM as a Cloud Service users: Upgrade to version 2025.5.0 or later, which will be automatically deployed through the Cloud Manager pipeline
- After upgrading, verify the fix by confirming the updated version number in AEM System Overview
- Test the affected form fields to ensure legitimate functionality remains intact after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46888 — 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-46888 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