CVE-2022-30679
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 confidenceThis is a reflected Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.14 and earlier. The attack requires social engineering to convince a victim to click a specially crafted URL containing malicious JavaScript in a parameter. When the victim visits the URL, the JavaScript executes within their browser context, potentially allowing session hijacking or data theft.
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 your Adobe Experience Manager versionAccess the AEM Welcome page (typically at /aem/start.html) or check the version via the system console at /system/console/bundles. The version number is displayed on the AEM Welcome screen or in the about Adobe Experience Manager information (go to Help > About Adobe Experience Manager).Affected if The installed version is earlier than 6.5.15.0 for AEM on-prem, or earlier than 2022.10.0 for AEM Cloud Service.
-
Identify exposed web endpoints that accept URL parametersReview your AEM instance for any custom servlets, sling selectors, or components that read request parameters (request.getParameter) and render them in HTML responses. Check under /apps and /libs for custom code. Use the Sling JSP script debugger or search for JSP/HTL files containing request.getParameter calls that output to the page.Affected if Your instance has custom or third-party endpoints that accept user-supplied URL parameters and reflect them directly into HTML without encoding.
-
Test for reflected parameter reflection in responsesUsing a browser or HTTP tool (such as Burp Suite or curl), send a request to suspected endpoints with a harmless test string (for example, ?param=<script>test</script>) in the URL. Capture the HTTP response and examine whether the raw <script> tag appears unencoded in the response body.Affected if The test string appears literally as <script>test</script> in the response without being HTML-encoded (e.g., as <script>).
-
Verify XSSAPI encoding is applied to user inputsReview the JSP, HTL, or Java code handling your endpoints. Search for occurrences of xssApi.encodeForHTML() or similar encoding functions applied to any request parameter before it is written to the response. Ensure all user-supplied values go through encoding.Affected if User-supplied parameters are written to responses without passing through AEM's XSSAPI encoding functions.
You are affected if your AEM version is below 6.5.15.0 (or below 2022.10.0 for Cloud Service) AND your instance has endpoints that reflect URL parameters in HTML responses without proper output encoding.
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 output encoding and input validation to the vulnerable endpoint to neutralize malicious script content before rendering. AEM provides XSSAPI for proper encoding; ensure all user-supplied parameters are sanitized before being reflected back in HTML responses.
Experience Manager: >= 6.5.15.0 | Experience Manager Cloud Service: >= 2022.10.0
- 1. Create a complete backup of your current AEM instance including repository, database, and configuration files
- 2. Download Adobe Experience Manager version 6.5.15.0 (or later for on-premise) from Adobe Software Distribution
- 3. For AEM on-premise: Follow Adobe's official upgrade documentation to stop the instance, run the upgrade, and verify the migration
- 4. For AEM Cloud Service: The update will be applied automatically upon deployment of version 2022.10.0 or later
- 5. After upgrade, verify the fix by testing that the reflected XSS vulnerability is no longer exploitable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30679 — 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-30679 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