CVE-2025-46850
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-privileged attacker can inject malicious JavaScript into vulnerable form inputs, which persists in the system. When other users view pages containing these injected fields, the malicious script executes in their browsers, potentially enabling session hijacking or credential 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.
-
Identify the installed AEM versionAccess the AEM Welcome page or Help menu, then navigate to 'Version Information' to view the exact installed version number. Alternatively, check the 'com.adobe.granite.platform.version' property in the System Information console at /system/console/systeminfo.Affected if The installed version is below 6.5.23.0 for the 6.5.x release line, or below 2025.5.0 for the cloud-released version line.
-
Determine if AEM Forms module is in useCheck if the Forms add-on package is installed by navigating to Package Manager (/crx/packmgr) and looking for AEM Forms packages, or by accessing the Forms section in the AEM navigation menu.Affected if The AEM Forms module is installed and form creation functionality is accessible to users.
-
Inspect form field input validation settingsNavigate to the Form Container properties in AEM Forms or check the XSS protection configuration in the Adobe Granite XSSAPI settings at /libs/granite/xss/config.xml or through the XSS Protection console.Affected if Form fields lack proper output encoding or XSS protection rules are disabled or misconfigured.
-
Verify low-privileged user access to form editingLog in as a user with minimal permissions (such as a standard content author) and attempt to create or edit a form to confirm the attack surface exists for low-privileged accounts.Affected if Low-privileged users can access form creation or editing capabilities without elevated permissions.
-
Review stored form data for existing malicious scriptsQuery the JCR (Java Content Repository) for form field values containing script tags or suspicious JavaScript patterns. Use CRXDE Lite (/crx/de) to search nodes under /content or /var where form data is stored, or examine the HTML source of published form pages.Affected if Form fields contain persisted JavaScript code in attributes or values that would execute when rendered.
Your environment is affected if you are running AEM versions below 6.5.23.0 or below 2025.5.0, the Forms module is enabled, and users with low privileges can create or edit form fields without sufficient input sanitization.
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 by upgrading to Adobe Experience Manager 6.5.23 or later. Additionally, implement output encoding and Content Security Policy headers as defense-in-depth measures until patching is complete.
6.5.23.0 (for 6.5.x line) or 2025.5.0 (for newer release line)
- 1. Backup your current AEM instance including the repository, database, and configuration files.
- 2. Review the Adobe Experience Manager 6.5.23.0 or 2025.5.0 release notes for any migration or compatibility requirements.
- 3. Test the upgrade in a non-production environment first to verify compatibility with your custom code and integrations.
- 4. Run the upgrade using the Adobe Package Manager or author/publish instance upgrade procedure appropriate to your deployment model.
- 5. After upgrade, verify that the vulnerable form fields no longer accept unsanitized input by testing XSS payloads in the affected fields.
- 6. Clear AEM caches and rebuild any search indexes if required.
- 7. Deploy to production once validation is complete.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46850 — 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-46850 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