CVE-2022-24573
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) vulnerability in the admin interface in Element-IT HTTP Commander 7.0.0 allows unauthenticated users to get admin access by injecting a malicious script in the User-Agent field.
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 confidenceA stored cross-site scripting (XSS) vulnerability exists in the admin interface of Element-IT HTTP Commander 7.0.0. The vulnerability stems from improper sanitization of the User-Agent HTTP header field, allowing unauthenticated attackers to inject malicious scripts that execute within the admin interface 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>= 5.0.0, < 5.3.6= 7.0.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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Confirm HTTP Commander installationIdentify if Element-IT HTTP Commander is running in your environment by checking for the application service or checking HTTP responses for HTTP Commander signaturesAffected if The product is installed and running
-
Determine installed versionCheck the HTTP Commander version through the admin interface, application binaries, or version information file provided with the installationAffected if Version is >= 5.0.0 and < 5.3.6, or version equals 7.0.0
-
Verify admin interface accessibilityCheck if the HTTP Commander admin interface is accessible over the network, typically on the same port as the web application with /admin or administrative pathsAffected if Admin interface is exposed and accessible
-
Check User-Agent logging behaviorInspect HTTP server logs or admin interface to confirm that User-Agent header values are being captured and displayed within the admin panelAffected if User-Agent values are stored and visible in the admin interface without sanitization
Your environment is affected if HTTP Commander versions 5.0.0 through 5.3.5 or version 7.0.0 are installed and the admin interface displays User-Agent data without proper sanitization.
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 · scoped5.3.6
Implement proper input validation and output encoding for the User-Agent header in the admin interface. Additionally, apply Content Security Policy (CSP) headers to mitigate XSS execution.
5.3.6 (for 5.x branch) or 7.0.1+ (for 7.x branch)
- 1. Identify the currently installed Http Commander version by checking the application or license information
- 2. For version 5.x users: Upgrade to version 5.3.6 or later (the fix is included in 5.3.6)
- 3. For version 7.0.0 users: Upgrade to version 7.0.1 or later (check element-it.com for the latest stable 7.x release containing the security fix)
- 4. After upgrading, verify the User-Agent field is now properly sanitized before being stored or displayed in the admin interface
- 5. Review admin access logs to check for any historical exploitation attempts
Generated from the published advisory — verify against the referenced sources before acting.
- 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-24573 — 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-24573 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