CVE-2022-44467
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 6.5.14 and earlier allows a low-privileged attacker to inject malicious JavaScript into URLs. When victims are persuaded to visit these crafted URLs, the payload is reflected back and executed within their 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 whether your AEM instance is on-premise (self-hosted) or AEM Cloud Service. Check your infrastructure documentation or contact your AEM administrator to confirm the deployment model.Affected if Running any AEM Cloud Service or on-premise AEM installation without knowing the specific version.
-
Check on-premise AEM versionAccess the AEM Welcome page or navigate to Help > About Adobe Experience Manager to view the installed version number. Alternatively, check the version.properties file in the crx-quickstart directory if you have file system access.Affected if The installed version is 6.5.14.x or earlier (anything below 6.5.15.0).
-
Check AEM Cloud Service versionAccess the AEM Cloud Service environment details through the Adobe Cloud Manager console or check the release notes associated with your deployment. Verify the version identifier shown for your Cloud Service instance.Affected if The Cloud Service version is earlier than the 2022.10.0 release.
-
Understand the attack vectorNote that this is a reflected XSS vulnerability where malicious JavaScript is injected into URLs. The vulnerability exists in URL handling on affected AEM endpoints.Affected if You are running a vulnerable version and your users could potentially visit attacker-crafted URLs pointing to your AEM instance.
You are affected if your AEM on-premise version is below 6.5.15.0 or your AEM Cloud Service version is below the 2022.10.0 release, as both contain the fix for this reflected XSS vulnerability.
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 version 6.5.15 or later to obtain the security patch; additionally, implement output encoding and input validation on affected endpoints as a defense-in-depth measure.
AEM 6.5.15.0 (on-premise) or AEM Cloud Service 2022.10.0
- Upgrade Adobe Experience Manager on-premise to version 6.5.15.0 or later
- If using Adobe Experience Manager Cloud Service, upgrade to the 2022.10.0 release or later
- After upgrading, verify the XSS vulnerability is remediated by testing the affected endpoint
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.0 h
- Testing4.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,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-44467 — 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-44467 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