CVE-2023-6691
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 · uneditedCambium ePMP Force 300-25 version 4.7.0.1 is vulnerable to a code injection vulnerability that could allow an attacker to perform remote code execution and gain root privileges.
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 confidenceThe Cambium ePMP Force 300-25 wireless device version 4.7.0.1 contains a code injection vulnerability in its web management interface. Attackers can inject malicious commands through unsanitized input parameters, achieving unauthenticated remote code execution with root-level system privileges.
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= 4.7.0.1CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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 device modelAccess the device web interface or check the device label/MAC OUI. Cambium ePMP devices use MAC addresses starting with 00:xx:xx or 64:xx:xx. Navigate to the Status or Device Info page in the web UI to confirm the model is ePMP Force 300-25.Affected if The device model is NOT ePMP Force 300-25 (different models may have different vulnerability status)
-
Check the installed firmware versionIn the device web interface, go to Status > Device Status or a similar section that displays firmware version. Alternatively, access the device via CLI and run 'show version' or 'get system info' if available.Affected if The firmware version displayed is exactly 4.7.0.1
-
Verify the web management interface is enabledAttempt to access the device IP via HTTP/HTTPS in a browser. Confirm the Cambium ePMP login page loads. Check if TCP ports 80 or 443 are listening on the device by scanning the device IP with 'nmap -p 80,443 <device-ip>' from an authorized location.Affected if The web management interface is accessible and responds on ports 80 or 443
-
Confirm no external network restrictions is in placeReview the device configuration under Management > HTTP/HTTPS settings. Check if the web interface is bound to all interfaces (0.0.0.0) or restricted to internal interfaces only. Inspect any upstream firewall rules that may limit access to the management ports.Affected if The web interface is bound to all interfaces (0.0.0.0) with no IP access restrictions configured
You are affected if you have an ePMP Force 300-25 device running firmware version 4.7.0.1 with the web management interface enabled and accessible.
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 the vendor-supplied security patch or upgrade to a patched firmware version. If no patch is available, restrict network access to the device management interface and monitor for compromise indicators.
- Consultation4.0 h
- Implementation3.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,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6691 — 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-2023-6691 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