CVE-2025-46952
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-privilege authenticated attacker can inject malicious JavaScript payloads into vulnerable form input fields, which are then stored and executed in the browsers of subsequent users who view pages containing the injected content.
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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 check the product version through the system information console (typically at /system/console/config or via the About Adobe Experience Manager option in the left rail). Compare the version number to the affected ranges: versions below 6.5.23.0 or below 2025.5.0.Affected if The installed version is 6.5.22.x or earlier, or falls between 6.5.23.0 and 2025.5.0 (non-inclusive).
-
Determine if custom form components are deployedReview the AEM implementation for custom form fields, adaptive forms, or user-generated content components. Check /apps and /libs directories for custom form field components (look for cq:editConfig or form field components under /apps/*/components).Affected if Custom form field components exist in the implementation, as the vulnerability affects form input fields.
-
Verify low-privilege user access to form authoringReview the user group permissions and groups assigned to low-privilege accounts (such as content authors or community members). Check if these users have write access to form pages, comment sections, or user-generated content areas that render form fields.Affected if Low-privilege authenticated users have permission to create or edit content containing form fields.
-
Inspect for existing injected script contentSearch the AEM repository (via CRXDE Lite at /crx/de or the Query tool) for common XSS payloads in form-related content nodes. Query for JCR content nodes containing script tags, javascript: protocols, or onload/onerror attributes within form field values.Affected if Malicious script payloads are found stored in form-related content nodes.
Your environment is affected if the installed AEM version is below 6.5.23.0 or below 2025.5.0 AND low-privilege users have access to create or edit content in form fields.
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. As an interim control, implement strict input validation and output encoding on form fields, and configure Content Security Policy (CSP) headers to mitigate XSS execution.
6.5.23.0 (for 6.5.x line) or 2025.5.0 (for 2025.x line)
- 1. Identify the current Adobe Experience Manager version by checking the AEM welcome page or system console
- 2. Determine which release line (6.5.x or 2025.x) your instance belongs to
- 3. Plan the upgrade, preferably testing in a non-production environment first
- 4. Perform a complete backup of the current AEM instance including repository, configurations, and custom code
- 5. Upgrade AEM 6.5.x instances to version 6.5.23.0 or later
- 5b. OR upgrade 2025.x instances to version 2025.5.0 or later
- 6. Verify the upgrade was successful by checking the AEM version in the system console
- 7. Test that the stored XSS vulnerability is no longer exploitable in the affected form fields
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46952 — 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-46952 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