dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46849

MEDIUM · 5.4 CVSS v3.1 Published 2025-08-20
Fix available
A fix is available. Upgrade to 6.5.23.0 / 2025.5.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Adobe 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 confidence

Adobe Experience Manager versions 6.5.22 and earlier contain a stored Cross-Site Scripting vulnerability where low-privileged users can inject malicious JavaScript into form fields. The payload persists on the server and executes when other users view the affected page, allowing session hijacking, data theft, or defacement.

MitigationApply the vendor patch for AEM 6.5.22 or later. Until patched, implement input validation and output encoding on all form fields, and consider deploying a WAF rule to filter XSS payloads.

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
Experience ManagerApplication
Affected:< 6.5.23.0< 2025.5.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Adobe Experience Manager installation
    Access the AEM Welcome page at /libs/granite/security/content/login.html or check the footer of any AEM page for version information. Alternatively, query the AEM version endpoint at /system/console/components if available.
    Affected if The system is confirmed to be Adobe Experience Manager
  2. Determine installed AEM version
    Navigate to Help > About Adobe Experience Manager in the AEM console, or check the version file in the installation directory. Compare the version number against the affected ranges: < 6.5.23.0 for 6.5.x branches, or < 2025.5.0 for newer releases.
    Affected if The installed version is 6.5.22 or earlier, or falls below 2025.5.0
  3. Verify Forms or Core Components are in use
    Check if the AEM Forms module or Core Components that render form fields are installed and enabled. Navigate to /libs/granite/ui/components/foundation or check the Forms console at /aem/forms (if available).
    Affected if Forms or form-rendering components are present and active on the instance
  4. Confirm low-privileged user access to form fields
    Review user permissions in the AEM Groups console at /security/groups.html. Identify if standard users or content authors have create or edit access to form components, Adaptive Forms, or content fragments that render in user-facing pages.
    Affected if Low-privilege users (non-admin) have permission to create or edit form content that other users can view

A user is affected if running AEM version 6.5.22 or earlier (or pre-2025.5.0) with Forms or form-enabled components, where low-privileged users can inject content into fields that are rendered to other users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.5.23.0 / 2025.5.0 or later
Fixed in 6.5.23.02025.5.0
Interim mitigation

Apply the vendor patch for AEM 6.5.22 or later. Until patched, implement input validation and output encoding on all form fields, and consider deploying a WAF rule to filter XSS payloads.

Recommended fix High confidence

AEM 6.5.23.0 or AEM 2025.5.0 (depending on your release train)

  1. 1. Identify your current Adobe Experience Manager version by checking the product version in the AEM About console or system/console/bundles
  2. 2. If running AEM 6.5.x version <= 6.5.22, plan upgrade to 6.5.23.0
  3. 3. If running AEM 2025.x version <= 2025.4.x, plan upgrade to 2025.5.0
  4. 4. Review Adobe's official release notes and upgrade documentation for the target version before proceeding
  5. 5. Perform a full backup of the AEM instance, including repository, database, and configurations
  6. 6. Test the upgrade in a non-production environment first
  7. 7. Apply the upgrade following Adobe's standard upgrade procedures
  8. 8. Verify the upgrade was successful and all bundles are in active state
Caveat Patch releases (e.g., 6.5.22 to 6.5.23) typically have minimal breaking changes; review release notes for any configuration or API changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Experience Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-46849 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-46849 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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