CVE-2022-30768
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 · uneditedA Stored Cross Site Scripting (XSS) issue in ZoneMinder 1.36.12 allows an attacker to execute HTML or JavaScript code via the Username field when an Admin (or non-Admin users that can see other users logged into the platform) clicks on Logout. NOTE: this exists in later versions than CVE-2019-7348 and requires a different attack method.
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 confidenceA stored XSS vulnerability exists in ZoneMinder 1.36.12 where malicious JavaScript can be injected into the Username field. When an administrator or any user with visibility into other logged-in users clicks Logout, the unsanitized username is rendered in the UI, triggering code execution. This is a persistent XSS requiring a different attack vector than the earlier CVE-2019-7348.
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= 1.36.12CVSS 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.
-
Verify ZoneMinder version is 1.36.12Check the ZoneMinder web interface under Help > About, or inspect the version file in the installation directory (e.g., /usr/share/zoneminder or package metadata)Affected if The installed version is exactly 1.36.12 (this specific version is affected; other versions may have different vulnerability status)
-
Confirm user management module is accessibleNavigate to the ZoneMinder web console and verify access to the Users or Options > Users section where usernames are defined and managedAffected if User management is enabled and you have permission to view or add users
-
Inspect existing usernames for suspicious contentIn the Users admin panel, examine all username entries for any containing HTML tags, script elements, or JavaScript event handlers (e.g., <script>, onerror=, onload=)Affected if Any username contains raw HTML or JavaScript code that could execute when rendered
-
Verify logout functionality displays usernamesLog in as an administrator or a user with visibility to other logged-in users, then access the logout function or user status page to observe if usernames are rendered without apparent encodingAffected if The logout page or user status display renders usernames in an unencoded manner
You are affected if running ZoneMinder 1.36.12 and any user account contains malicious script in the username field, which executes when viewed by an admin or user with visibility to other users on logout or user listing pages.
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.
From vendor dataApply input validation and output encoding on the Username field throughout the application, particularly in the user listing and logout functionality. Consider upgrading to the latest ZoneMinder version if a patch is available.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30768 — 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-30768 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