CVE-2024-26118
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.19 and earlier are affected by a reflected Cross-Site Scripting (XSS) vulnerability. If an 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 confidenceAdobe Experience Manager versions 6.5.19 and earlier contain a reflected Cross-Site Scripting (XSS) vulnerability where malicious JavaScript can be injected via crafted URLs and executed within a victim's browser when they visit the malicious link.
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.20.0< 2024.3.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 installed AEM versionAccess the AEM Welcome page and look for the version number in the bottom-left corner, or query the system console at /system/console/systeminfo to retrieve the detailed product version information.Affected if The displayed version is 6.5.19 or earlier, or falls below 2024.3.0, indicating the instance is within the vulnerable range.
-
Confirm AEM is runningAccess the AEM instance via its hostname or IP address on the typical port (typically 4502 for author or 80/443 for publish). Verify the login page or welcome screen loads.Affected if The AEM instance is accessible and running, making it a potential target for exploitation.
-
Check if vulnerable endpoints are exposedReview the AEM instance for accessible paths that accept user-supplied input via URL parameters, particularly on publish-facing instances. Look for parameters that reflect input back into the response without encoding.Affected if Input-reflection-capable endpoints are exposed without input validation or output encoding protections in place.
An AEM instance is affected if it is running version 6.5.19 or earlier, or any version prior to 2024.3.0, and has accessible endpoints that could accept malicious crafted URLs.
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.20.02024.3.0
Upgrade to a patched version of Adobe Experience Manager beyond 6.5.19, or implement input validation and output encoding on the vulnerable endpoint(s) to neutralize XSS vectors.
AEM 6.5.20.0 (for 6.5.x line) or AEM 2024.3.0 (for as-a-cloud-service line)
- 1. Identify the current Adobe Experience Manager version in use
- 2. For AEM 6.5.x releases: Plan upgrade to version 6.5.20.0 or later
- 3. For AEM as a Cloud Service: Plan upgrade to version 2024.3.0 or later
- 4. Review Adobe's official upgrade documentation for your specific release line
- 5. Perform upgrade in a non-production environment first
- 6. Validate the upgrade and test for the XSS fix
- 7. Deploy the upgraded version to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26118 — 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-2024-26118 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