CVE-2026-32298
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 · uneditedThe Angeet ES3 KVM does not properly sanitize user-supplied variables parsed by the 'cfg.lua' script, allowing an authenticated attacker to execute OS-level commands.
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 confidenceCommand injection vulnerability in Angeet ES3 KVM's cfg.lua script where user-supplied variables are not properly sanitized, allowing authenticated attackers to execute arbitrary OS commands.
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 dataall versionsCVSS 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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
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 the installed KVM productCheck the device model and firmware version through the KVM interface or system documentation. Look for 'Angeet ES3 KVM' or similar branding in the management web interface or device labeling.Affected if The product is Angeet ES3 KVM firmware of any version.
-
Locate the cfg.lua scriptAccess the KVM filesystem or web directory structure. The cfg.lua script is typically found in the web management directory (often /cgi-bin/cfg.lua or similar paths under the web root). Use file listing commands if you have shell access, or attempt to access it via HTTP.Affected if The cfg.lua script exists and is accessible via the web interface.
-
Verify authentication is enabledCheck the KVM management interface security settings. Confirm that authentication is required for accessing the cfg.lua endpoint. Look for login sessions, credential requirements, or authentication configuration in the system settings.Affected if Authentication is not enforced or can be bypassed, allowing unauthenticated access to cfg.lua.
-
Assess network exposure of the KVM management interfaceDetermine if the KVM web management port (typically HTTP/HTTPS on common ports) is exposed to untrusted networks. Use network scanning (nmap, netstat) to identify listening interfaces and perform a port scan from an untrusted endpoint to verify accessibility.Affected if The KVM management interface is reachable from untrusted networks or the internet.
Your environment is affected if you run Angeet ES3 KVM firmware with the cfg.lua script accessible and the management interface exposed to network locations where untrusted attackers could obtain valid credentials.
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 vendor firmware patch when available; until then, restrict network access to the KVM management interface to trusted IPs only and use strong authentication credentials.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32298 — 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-2026-32298 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