CVE-2025-46927
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 stored in the system. When other users view pages containing these compromised 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.
-
Determine AEM product versionAccess the AEM Welcome page or check the JAR file properties. Navigate to Help > About Adobe Experience Manager, or query the system console at /system/console/status-productinfo to retrieve the installed version number.Affected if The installed version is 6.5.22 or earlier, or falls below version 2025.5.0 for the newer release line.
-
Identify custom form field implementationsReview custom component XML definitions in /apps for form input components (specifically those extending foundation/components/form or coralui components). Check for fields that accept user input and are stored in the repository without output encoding.Affected if Custom form components exist that do not apply server-side output encoding or validation before rendering stored content.
-
Audit stored content in form-enabled pagesQuery the JCR repository using CRXDE Lite or a tool like the AEM Query Builder to search for HTML or script tags stored in form-related nodes under /content or /home. Example: search for nodes containing '<script' or 'javascript:' patterns.Affected if Stored content contains unsanitized HTML, script tags, or event handler attributes in user-controllable form fields.
-
Review Content Security Policy headersCheck the dispatcher configuration or the Apache HTTP Server configuration for CSP header definitions. Look for headers like Content-Security-Policy in the Apache config files or AEM sling filter configurations.Affected if CSP headers are missing, overly permissive (using 'unsafe-inline' or 'unsafe-eval'), or not configured to block script execution from untrusted sources.
-
Check for low-privileged user access to form componentsVerify group permissions in AEM User Admin console (/useradmin) to determine if low-privileged users (contributors, community members) have write access to form components or user-generated content areas.Affected if Low-privileged users can author or modify content in form fields that render on published pages.
Your environment is affected if the installed AEM version is below 6.5.23.0 or 2025.5.0 AND custom form fields exist that render user-supplied content without encoding, or if stored malicious scripts are already present in the repository.
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 AEM to a version newer than 6.5.22 or apply the vendor-provided patch. Until patched, implement strict input validation and output encoding on form fields, and configure Content Security Policy headers to mitigate XSS execution.
6.5.23.0 (for 6.5.x on-premises); 2025.5.0 (for AEM as a Cloud Service)
- Identify your current Adobe Experience Manager version and product line (6.5.x on-premises or cloud/2024.x)
- For AEM 6.5.x on-premises: Upgrade to version 6.5.23.0 or later
- For AEM as a Cloud Service / 2024.x: Upgrade to version 2025.5.0 or later
- After upgrading, verify that the form fields previously vulnerable to XSS are properly sanitized
- Test that legitimate form functionality still works as expected after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46927 — 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-46927 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