CVE-2025-46923
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 confidenceA stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.22 and earlier allows low-privileged attackers to inject malicious JavaScript into form fields. The malicious payload persists in the system and executes in victim users' browsers when they navigate to pages containing the affected form 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.
-
Identify AEM installation and versionAccess the AEM welcome page or check the system/console (typically at /libs/granite/core/content/login.html or /system/console/bundles). The version is often displayed in the footer of the AEM welcome page or obtainable via the API at /api.json?path=/Affected if The installed version is less than 6.5.23.0 or less than 2025.5.0
-
Determine if Forms functionality is enabledNavigate to the AEM Forms interface (typically at /aem/forms or check for form-related workflows in /libs/fd/fm). Look for any custom or adaptive forms that accept user input.Affected if AEM Forms or any form creation/submission functionality is in use, as the XSS vulnerability exists within form fields
-
Verify low-privileged user access to formsLog in with a low-privileged user account (such as a standard 'user' or 'contributor' role) and attempt to access form creation or submission interfaces. Check user permissions under /useradmin or /security/usersAffected if Low-privileged users can create, edit, or submit forms containing the vulnerable fields
-
Inspect stored form data for suspicious payloadsQuery the AEM repository (via CRXDE Lite at /crx/de or the Query tool) for form submission data in /content/forms or similar paths. Search for common XSS patterns like <script, javascript:, onload, onerror in field values.Affected if Form submission records contain unsanitized HTML or JavaScript code that could execute in a victim's browser
-
Review form field input validation settingsExamine form field definitions in the Form Model (at /libs/fd/fm/gui/components/admin/fmclient/formModel or via the Forms Editor). Check if output encoding or input validation is configured for the fields.Affected if Form fields lack strict input validation and output encoding configurations, leaving them vulnerable to XSS injection
You are affected if your AEM version is below 6.5.23.0 or below 2025.5.0 AND you have Forms with fields accessible to low-privileged users without proper input validation.
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. As a defense-in-depth measure, implement strict input validation and output encoding on all form fields.
Adobe Experience Manager 6.5.23.0 (on-premise) or 2025.5.0 (cloud/newer releases)
- 1. Identify the current Adobe Experience Manager version in use by checking the AEM SDK or system information
- 2. For AEM 6.5.x on-premise installations: Plan upgrade to version 6.5.23.0 or later
- 3. For AEM as a Cloud Service or newer releases: Plan upgrade to version 2025.5.0 or later
- 4. Review the Adobe Experience Manager upgrade documentation for your deployment type
- 5. Create a backup of the current AEM instance and content repository before upgrading
- 6. Test the upgrade in a non-production environment first
- 7. Execute the upgrade following Adobe's recommended procedures
- 8. Verify the upgrade was successful and test that the application functions correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46923 — 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-46923 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