Experience ManagerApplication · Adobe

CVE-2019-7955

MEDIUM · 6.1 CVSS v3.0 Published 2019-07-18
Fix available
A fix is available. Upgrade to after 6.5 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 version 6.4 and ealier have a Reflected Cross-site Scripting vulnerability. Successful exploitation could lead to Sensitive Information disclosure in the context of the current user.

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.4 and earlier contain a reflected Cross-Site Scripting (XSS) vulnerability. Attackers can inject malicious scripts through vulnerable parameters, which are reflected back to the user without proper sanitization. Successful exploitation allows theft of sensitive information such as session cookies, authentication tokens, or other user data in the context of the current user session.

MitigationUpgrade Adobe Experience Manager to a version newer than 6.4 that includes the security patch. Additionally, implement output encoding and input validation on all user-supplied parameters as a defense-in-depth measure.

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.2, <= 6.5

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/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. Check the Adobe Experience Manager version
    Access the AEM welcome page (http://yourserver:4502/welcome.html) or the System Information console at /system/console/config/com.adobe.granite.infocollector.impl.SystemInfoCollector, or run the command: curl -s http://yourserver:4502/libs/granite/core/content/login.html?resource=/libs/granite/core/content/login.html 2>/dev/null | grep -o 'version"[^"]*' to see version details
    Affected if The installed version is 6.2, 6.3, 6.4, or 6.5
  2. Verify the AEM version via the bundles console
    Navigate to /system/console/bundles and look for the 'Adobe Experience Manager Core' bundle in the list; the Version column displays the exact AEM version installed
    Affected if The version shown is between 6.2 and 6.5 inclusive
  3. Confirm the affected parameter endpoints are accessible
    Test for reflected XSS parameters by accessing common AEM query parameter endpoints such as /libs/granite/core/content/login.html?resource=TEST or other URL parameters on any AEM page - check if the input is reflected unsanitized in the response
    Affected if User-supplied parameters in URLs are returned in the HTML response without encoding or sanitization
  4. Check for custom input validation on the publish tier
    Review any custom filter or servlet configurations in /system/console/config that handle request parameters, and verify if input validation or output encoding is explicitly configured for user-controllable parameters
    Affected if No custom input validation filters are deployed and the AEM version falls within the affected range

A system is affected if it runs Adobe Experience Manager version 6.2 through 6.5 and reflects unsanitized user input back in HTTP responses.

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.

From vendor data
Upgrade available Upgrade to a release after 6.5
Interim mitigation

Upgrade Adobe Experience Manager to a version newer than 6.4 that includes the security patch. Additionally, implement output encoding and input validation on all user-supplied parameters as a defense-in-depth measure.

Fix this in Experience Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-7955 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-7955 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