CVE-2022-42360
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 version 6.5.14 (and earlier) is 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 confidenceReflected Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager version 6.5.14 and earlier. An attacker can inject malicious JavaScript into a URL parameter that gets reflected back in the HTTP response, executing within the victim's browser when they visit the crafted URL.
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.15.0< 2022.10.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.
-
Check Adobe Experience Manager versionAccess the AEM Welcome page or run the version check: Navigate to /system/console/productinfo or check the crx-quickstart/conf folder for the version.properties file. The version is typically displayed in the AEM About Adobe Experience Manager page accessible from the top-left menu in the AEM start page.Affected if The installed version is 6.5.14.0 or earlier, or the Cloud Service version is before 2022.10.0
-
Identify exposed web tier endpointsReview the AEM publish tier web.xml file at /opt/aem/author/crx-quickstart/conf/web.xml or check which servlets and filters are mapped to URL paths. Look for any publicly accessible endpoints that process URL parameters.Affected if User-facing endpoints that accept URL parameters are exposed on the publish or author tier without proper validation
-
Test for reflected parameter reflectionIf you have access to a test environment, construct a test URL with a unique marker in a suspected parameter (e.g., /path/to/endpoint?param=<test123>). Make an HTTP request and inspect the response body to see if the exact marker value appears unencoded in the HTML response.Affected if The parameter value from the URL is reflected back in the HTTP response without HTML encoding (visible as raw <test123> rather than <test123>)
A user is affected if their AEM installation is version 6.5.14.0 or earlier (or Cloud Service before 2022.10.0) AND they have publicly accessible endpoints that reflect URL parameter values directly into HTML responses.
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.15.02022.10.0
Upgrade Adobe Experience Manager to a version beyond 6.5.14 that includes the security patch. As a temporary measure, implement URL parameter validation and output encoding on affected endpoints.
AEM On-Premise: 6.5.15.0 | AEM Cloud Service: 2022.10.0
- 1. Identify whether you are using Adobe Experience Manager on-premise or Adobe Experience Manager Cloud Service
- 2. For AEM on-premise: Upgrade Adobe Experience Manager to version 6.5.15.0 or later
- 3. For AEM Cloud Service: Ensure your environment is updated to the 2022.10.0 release or later
- 4. After upgrading, verify the XSS fix is applied by testing the vulnerable endpoint referenced in the security bulletin
- 5. Clear any caches and rebuild any custom applications if necessary to ensure compatibility with the updated version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42360 — 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-2022-42360 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