dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-49534

MEDIUM · 5.4 CVSS v3.1 Published 2025-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 FP11.4 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. Scope is changed.

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 FP11.4 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability in form fields. A low-privilege attacker can inject malicious JavaScript that executes in victim browsers when they view pages containing the compromised fields. The CVSS scope change indicates the vulnerability impacts resources beyond the vulnerable component.

MitigationImplement proper input validation and output encoding/sanitization on all form fields in AEM to neutralize malicious script payloads before storage and before rendering. Apply AEM security patches or upgrades to FP11.5 or later.

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.22.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 AEM version
    Access the AEM welcome page or use the version indicator (/system/console/systeminfo) to determine the installed AEM version. Compare against 6.5.22.0 and earlier versions.
    Affected if Installed version is 6.5.22.0 or any version prior to FP11.5 update.
  2. Confirm form field usage
    Review the AEM instance for sites using form components, adaptive forms, or custom form fields that accept user input and store data.
    Affected if The AEM instance hosts pages or components containing form fields that capture and store user-submitted data.
  3. Verify content viewing access
    Check user permissions and content structure to determine if low-privilege users can submit form content that is subsequently rendered and viewed by other users.
    Affected if Low-privilege authenticated users can create or edit form content that gets displayed on pages accessible to other users.
  4. Inspect stored form data for payloads
    Query the repository (via CRXDE Lite or AEM Groovy console) for stored form field content, looking for script tags, event handlers, or javascript: URIs in form field values.
    Affected if Form field data in the repository contains unsanitized HTML or JavaScript syntax that could execute in a browser.

You are affected if running AEM version 6.5.22.0 or earlier AND the instance uses form fields where low-privilege users can inject and store content that other users view in their browsers.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding/sanitization on all form fields in AEM to neutralize malicious script payloads before storage and before rendering. Apply AEM security patches or upgrades to FP11.5 or later.

Recommended fix Moderate confidence

Adobe Experience Manager 6.5.22 with Feature Pack FP11.5 or later

  1. Verify current Adobe Experience Manager version and installed Feature Pack (FP) level in AEM System Overview or through the version.properties file
  2. Review Adobe Experience Manager 6.5.22 release notes and Feature Pack FP11.5 (or latest available) release notes for compatibility considerations
  3. Create a full backup of the AEM repository (crx-quickstart) and database before proceeding
  4. Test the upgrade in a non-production environment first
  5. Stop all AEM instances (author and publish)
  6. Apply the Feature Pack FP11.5 or later upgrade following Adobe's documented upgrade procedure
  7. Verify the upgrade was successful by checking the AEM version in System Overview
  8. Clear the AEM cache and rebuilt any indexes if required
Caveat AEM feature pack upgrades may introduce compatibility changes with custom components or integrations; thorough testing in non-production is recommended 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 help mitigating

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-49534 — 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-49534 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