CVE-2024-40891
**UNSUPPORTED WHEN ASSIGNED** A post-authentication command injection vulnerability in the management commands of the legacy DSL CPE Zyxel VMG4325-B10A firmware version 1.00(AAFR.4)C0_20170615 could allow an authenticated attacker to execute operating system (OS) commands on an affected device via Telnet.
do firstThe impacted product could be end-of-life (EoL) and/or end-of-service (EoS). Users should discontinue product utilization if a current mitigation is unavailable.
Can a WAF block it? No. The vulnerability is exploited via Telnet, which is a non-HTTP protocol. Therefore, a web application firewall cannot filter or block the malicious input.
Also consider: shlex/execve-style APIs
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2024-40891 being exploited?
Yes. CVE-2024-40891 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-40891?
CVE-2024-40891 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-40891?
Yes. A fix has been recorded for CVE-2024-40891. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-40891 affect?
CVE-2024-40891 affects zyxel:vmg1312-b10a_firmware, zyxel:vmg1312-b10b_firmware, zyxel:vmg1312-b10e_firmware, zyxel:vmg3312-b10a_firmware, and 10 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected<= 1.00
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Unvetted proof-of-concept code on GitHub: 2 GitHub proofs of concept
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 11 Feb 2025 (SSVC 2.0.3).
timeline
- 4 Feb 2025Published
- 11 Feb 2025Added to CISA KEV (exploited in the wild) · 7 days later
- 11 Feb 2025CISA SSVC assessment: exploitation active · 1 day later
- 4 Mar 2025CISA remediation due date (US federal agencies) · 20 days later
- 21 Oct 2025CVE record last updated · 232 days (about 8 months) later
- 13 Aug 2026First proof-of-concept repository on GitHub (unvetted) · 295 days (about 10 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 82 days (about 3 months) later
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.