CVE-2025-46946
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 vulnerability in form fields. A low-privilege authenticated attacker can inject malicious JavaScript payloads into vulnerable input fields, which persist on the page. When other users view or interact with the affected page, the embedded script executes in their browser context, potentially stealing session cookies or performing actions on behalf of the victim.
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 AEM versionAccess the AEM System Information console at /system/console/configMgr or check the version.properties file in the crx-quickstart directory. Alternatively, append /libs/granite/core/content/login.html to your AEM base URL to view version information on the login screen.Affected if The installed version is 6.5.22 or earlier, or falls below version 2025.5.0 (for newer release trains). Compare the installed version against the affected ranges < 6.5.23.0 or < 2025.5.0.
-
Confirm AEM Forms or custom form components are in useNavigate to the AEM Forms console at /aem/forms.html or inspect the content repository under /content for form-based pages or adaptive forms. Check for presence of form field components in the /libs or /apps directories.Affected if AEM Forms, adaptive forms, or custom form components that accept user input are actively deployed or enabled on the instance.
-
Verify low-privilege user access to form authoringReview the Content Access Control List (ACL) permissions under /useradmin. Specifically check if standard authenticated users (non-admin) have permission to submit forms, create or edit form content, or access the forms editor interface.Affected if Low-privilege authenticated users (contributors, authors, or limited group members) have write or create permissions on form-related content paths.
-
Inspect form field configurations for missing output encodingReview the form component XML configuration files under /apps or /libs, such as .xml files for adaptive form fields or core form components. Check if the field properties explicitly disable server-side validation or output encoding settings.Affected if Form fields are configured with allowHTML or disableHtmlEscaping set to true, or server-side output encoding is explicitly disabled on input field components.
You are affected if your AEM version is below 6.5.23.0 or below 2025.5.0, forms are in use, and low-privilege users can inject content into form fields 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
Apply the vendor patch for CVE-2025-46946 (AEM version 6.5.23 or later). Additionally, implement output encoding and input validation on all form fields as a defense-in-depth measure until the patch can be deployed.
AEM 6.5: upgrade to 6.5.23.0 or later; AEM as a Cloud Service: upgrade to 2025.5.0 or later
- Identify your current Adobe Experience Manager version by checking the Product Information page in AEM or the system console
- For AEM 6.5 on-premise: Plan an upgrade to version 6.5.23.0 or later
- For AEM as a Cloud Service: Ensure your environment is updated to the 2025.5.0 release or later
- Review Adobe's upgrade documentation for your deployment type (on-premise or Cloud Service)
- Schedule a maintenance window and perform a backup of your current AEM instance
- Execute the upgrade following Adobe's recommended upgrade procedure
- After upgrade, verify the AEM version reflects 6.5.23.0 or later (for 6.5) or confirm the Cloud Service deployment includes 2025.5.0
- Test critical form workflows to ensure functionality is maintained post-upgrade
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-46946 — 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-46946 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