CVE-2025-46968
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 that persists in the form data and executes in victim browsers when they 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.
-
Determine installed AEM versionAccess the AEM Welcome page or check the product version via the system information console (typically at /system/console/bundles or through the AEM version file in the installation directory). Compare the version number to the affected ranges: < 6.5.23.0 or < 2025.5.0.Affected if The installed version is 6.5.22 or earlier, or falls between 6.5.23.0 and 2025.5.0 (exclusive of 2025.5.0).
-
Verify presence of AEM FormsCheck if the AEM Forms module is installed and enabled in the environment. This can be done by accessing the AEM console and looking for Forms-related capabilities or by checking for form-related packages in the package manager.Affected if AEM Forms is installed and active in the environment, as the XSS vulnerability exists in form fields.
-
Review low-privilege user access to form authoringExamine the user group permissions in AEM to determine if low-privilege users (non-admin users) have access to create or edit forms. Check user group configurations under the Users or Groups console.Affected if Low-privilege users have permissions to author or edit form fields, enabling them to inject malicious scripts.
-
Inspect stored form data for suspicious contentUse the AEM query builder or CRX/DE to search for form field data in the repository. Look for patterns commonly associated with XSS payloads such as <script>, javascript:, onload, onerror, or other HTML/script tags within form field values.Affected if Form data in the repository contains unescaped HTML or script tags that could execute in victim browsers.
You are affected if your AEM version is below 6.5.23.0 (or below 2025.5.0) AND you have AEM Forms enabled with low-privilege users having form authoring permissions, as the stored XSS can only be exploited under these conditions.
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 Adobe Experience Manager version 6.5.23 or later. Until patched, restrict low-privilege user permissions on form authoring and implement Content Security Policy headers as a compensating control.
6.5.23.0 (on-premise) or 2025.5.0 (cloud services)
- Upgrade Adobe Experience Manager to version 6.5.23.0 or later (for on-premise 6.x)
- If using AEM cloud services, upgrade to 2025.5.0 or later
- After upgrade, verify the fix by testing that form fields no longer allow script injection
- Review Adobe's release notes for any additional required post-upgrade configurations
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46968 — 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-46968 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