CVE-2022-42365
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 XSS vulnerability in Adobe Experience Manager 6.5.14 and earlier allows low-privilege attackers to execute malicious JavaScript in victim browsers by tricking users into visiting specially crafted URLs pointing to vulnerable pages.
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 AEM versionNavigate to the AEM Welcome page or check the product version through the system information console (/system/console/configMgr or by checking the crx-quickstart/package/version.txt file)Affected if The installed version is Adobe Experience Manager 6.5.14.0 or earlier, or the version string shows a build earlier than 6.5.15.0
-
Check AEM Cloud Service releaseIf using Adobe Experience Manager Cloud Service, verify the current release version through the Cloud Manager UI or the environment details in the Adobe Admin ConsoleAffected if The Cloud Service release version is earlier than 2022.10.0
-
Identify accessible external-facing endpointsReview the AEM publish instances and any externally accessible content pages that accept user input through URL parametersAffected if Public-facing pages with unauthenticated input parameters are accessible without additional access controls
-
Test for reflected parameter reflectionUsing a test browser or HTTP tool, append a benign test string (such as a unique alphanumeric value) to suspected URL parameters on accessible pages and observe if the value is reflected in the rendered HTML without encodingAffected if User-supplied URL parameter values appear unencoded in the response HTML, indicating potential XSS vulnerability
-
Verify if input validation or output encoding is implementedInspect the affected endpoint's JSP, HTL, or servlet code to determine if proper output encoding (using AEM encoding utilities) or input validation is applied to the reflected parametersAffected if No output encoding or input validation is found for the vulnerable parameter, leaving it exploitable
You are affected if your AEM 6.5.x version is earlier than 6.5.15.0 or your AEM Cloud Service release is earlier than 2022.10.0 and you have externally accessible pages with unencoded URL parameter reflection.
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
Apply the vendor patch for CVE-2022-42365. Additionally, implement output encoding and input validation on the affected endpoint(s) to prevent XSS execution.
Adobe Experience Manager 6.5.15.0 (on-premise) or 2022.10.0 (Cloud Service)
- For Adobe Experience Manager on-premise (6.5.x): Upgrade to version 6.5.15.0 or later
- For Adobe Experience Manager Cloud Service: Ensure the environment is updated to version 2022.10.0 or later
- Verify the upgrade by testing the application to confirm the XSS vulnerability is no longer present
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42365 — 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-42365 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