CVE-2022-42350
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 · moderate confidenceReflected XSS vulnerability in Adobe Experience Manager 6.5.14 and earlier versions. An attacker crafts a malicious URL containing JavaScript payload and tricks a low-privileged victim into visiting it, causing the script to execute in the victim's browser context.
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.
-
Identify AEM deployment typeDetermine if your environment is Adobe Experience Manager on-premise/managed services or Adobe Experience Manager Cloud Service. Check your AEM console, licensing portal, or deployment documentation.Affected if The environment is either AEM on-premise/managed services or AEM Cloud Service.
-
Check AEM on-premise versionAccess the AEM Welcome page or navigate to Tools > Operations > Diagnosis > Version Info. Alternatively, check the version.properties file in the crx-quickstart folder or query the JMX console for the Product Version MBean.Affected if The installed version is 6.5.14.0 or earlier (any version below 6.5.15.0).
-
Check AEM Cloud Service versionAccess the Cloud Manager UI or check the release notes for your Cloud Service environment. The version information is typically available in the environment details or release documentation.Affected if The Cloud Service version is earlier than the 2022.10.0 release.
-
Verify current patch levelReview installed hotfixes and service packs via the AEM Package Manager (http://host:port/crx/packmgr) or the Software Distribution portal. Cross-reference with Adobe security bulletin APSB22-46.Affected if No hotfix for CVE-2022-42350 (APSB22-46) is installed and version remains below 6.5.15.0 (on-premise) or before 2022.10.0 (Cloud Service).
Your environment is affected if you run AEM on-premise below version 6.5.15.0, or AEM Cloud Service before the 2022.10.0 release, and the corresponding security patch has not been applied.
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 Adobe's official security patch/hotfix for AEM 6.5.14 or later. Implement input validation and output encoding on the vulnerable parameter to neutralize the XSS vector.
Adobe Experience Manager 6.5.15.0+ (on-premise) or AEM Cloud Service 2022.10.0+
- For Adobe Experience Manager 6.5 on-premise: Upgrade to version 6.5.15.0 or later
- For Adobe Experience Manager Cloud Service: Ensure deployment is on 2022.10.0 release or later
- After upgrading, verify the XSS protection is functioning by testing that malicious script content in URLs is properly escaped/not executed
- Consult Adobe's official release notes for 6.5.15.0 and Cloud Service 2022.10.0 for any additional required configuration changes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42350 — 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-42350 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