dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46875

MEDIUM · 5.4 CVSS v3.1 Published 2025-06-10
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 reflected Cross-Site Scripting (XSS) vulnerability. If a low privileged attacker is able to convince a victim to visit a URL referencing a vulnerable page, malicious JavaScript content may be executed within the context of the victim's browser.

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 reflected Cross-Site Scripting (XSS) vulnerability where malicious JavaScript can be injected into URLs. When a victim is persuaded to click a crafted URL pointing to a vulnerable page, the malicious payload executes within the victim's browser context, potentially allowing session hijacking or data theft.

MitigationUpgrade Adobe Experience Manager to a version newer than 6.5.22. Additionally, implement output encoding and input validation on affected endpoints to prevent XSS attacks.

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. Confirm Adobe Experience Manager is installed
    Check for AEM installation by looking for the crx-quickstart folder or AEM jar files in the application directory, or by accessing the AEM welcome page at /libs/granite/core/content/login.html on your web server
    Affected if AEM is not present on the system - this CVE only affects Adobe Experience Manager
  2. Identify the installed AEM version
    Access the AEM System Information console at /system/console/status-productinfo or check the version.properties file in the crx-quickstart folder, or look at the AEM jar file name which typically contains the version number
    Affected if Unable to retrieve version information - you cannot determine exposure without knowing the version
  3. Compare your version against affected ranges
    Check if the installed version is below 6.5.23.0 or below 2025.5.0. AEM versions follow the pattern major.minor.patch (e.g., 6.5.22.0) or year.month format (e.g., 2025.4.0)
    Affected if Your AEM version is 6.5.22.x or earlier, or 2025.4.x or earlier, meaning the reflected XSS vulnerability is present in your version
  4. Verify AEM web server is accessible
    Confirm the AEM instance is running and accessible over HTTP/HTTPS by accessing the login page or any content page on your AEM host
    Affected if The AEM web application is not running or accessible - the XSS requires a running AEM instance to be exploited through crafted URLs

You are affected if Adobe Experience Manager is installed and the running version is below 6.5.23.0 or below 2025.5.0, as these versions contain the reflected XSS vulnerability in URL handling.

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

Upgrade Adobe Experience Manager to a version newer than 6.5.22. Additionally, implement output encoding and input validation on affected endpoints to prevent XSS attacks.

Recommended fix High confidence

Adobe Experience Manager 6.5.23.0 or 2025.5.0 (or later)

  1. 1. Back up the current AEM instance including the repository (crx-quickstart) and any associated database
  2. 2. Review the Adobe Experience Manager 6.5.23.0 or 2025.5.0 release notes for changes, deprecated features, and known issues
  3. 3. Create a staging or development environment with an identical copy of the production instance
  4. 4. Perform the upgrade in the non-production environment first to validate compatibility with custom code, third-party integrations, and workflows
  5. 5. Schedule a maintenance window and notify users
  6. 6. Stop the AEM instance and ensure all processes have terminated
  7. 7. Run the upgrade installer for the target version (6.5.23.0 or 2025.5.0) following Adobe's official upgrade documentation
  8. 8. After upgrade, verify the /system/console/configMgr is accessible and check for any configuration migration prompts
Caveat AEM upgrades may introduce breaking changes including deprecated APIs, workflow modifications, and index changes; custom code and third-party integrations should be tested thoroughly in a non-production environment before production deployment

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Check whether your project pulls in CVE-2025-46875 — 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-46875 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