CVE-2025-46962
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. A low-privileged attacker can inject malicious JavaScript into vulnerable form fields, which gets persisted in the system. When other users browse to pages containing these compromised fields, the malicious script executes in their browsers, potentially enabling session hijacking or data theft.
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 Web Console or check the version.properties file in the crx-quickstart folder. Alternatively, navigate to /system/console/bundles or check the 'About Adobe Experience Manager' page in the AEM Welcome screen.Affected if The installed version is older than 6.5.23.0 or older than the 2025.5.0 release.
-
Identify accessible form endpointsReview published sites and check for form components (such as Adaptive Forms, Core Components forms, or custom form implementations) that accept user input. Use the AEM Sites audit log or review content structure under /content to locate form pages.Affected if Forms that accept user input are publicly or low-privileged user accessible without additional security controls.
-
Inspect form field content for malicious scriptsQuery the JCR repository using tools like CRXDE Lite (accessible at /crx/de) or the Query Builder API to search for stored form data containing script tags, javascript: URIs, or event handler attributes in nodes under /content where form submissions are stored.Affected if Form submission data contains unsanitized script tags, onload/onerror event handlers, or javascript: protocols that would execute in a user's browser.
-
Review Content Security Policy configurationCheck the Apache Sling header configuration or dispatcher .any files for CSP header rules. Look at the clientlibs under /libs/cq/security/ or custom clientlib folders for CSP meta tag or header definitions.Affected if No CSP headers are configured, or CSP allows 'unsafe-inline' or 'unsafe-eval' directives that would permit XSS execution.
You are affected if your AEM version is below 6.5.23.0 or below 2025.5.0 AND you have form fields that accept input from low-privileged users without proper 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
Upgrade Adobe Experience Manager to a version newer than 6.5.22. Additionally, implement input validation and output encoding on all form fields, and consider deploying Content Security Policy (CSP) headers to mitigate XSS execution.
Adobe Experience Manager 6.5.23.0 (for 6.5.x line) or 2025.5.0 (for newer release line)
- Identify your current Adobe Experience Manager version by checking the product about page or system console
- Review the Adobe Experience Manager 6.5.23.0 or 2025.5.0 release notes for upgrade requirements and compatibility information
- Ensure you have a complete backup of your AEM instance including the repository, database, and configuration files
- Create a staging or development environment to test the upgrade before production deployment
- Follow Adobe's official upgrade documentation for your specific AEM version to migrate to 6.5.23.0 or 2025.5.0
- After upgrade, verify that the vulnerable form fields no longer accept malicious script injection
- Deploy the upgraded version to production after successful validation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46962 — 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-46962 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