CVE-2026-40814
Unauthenticated SQLi in dataapi.php at _mb24confi_getTagAlarm.
Is CVE-2026-40814 being exploited?
Not confirmed. CVE-2026-40814 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.32% probability of exploitation in the next 30 days.
How severe is CVE-2026-40814?
CVE-2026-40814 is rated High with a CVSS score of 8.7. 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-2026-40814?
Yes. A fix has been recorded for CVE-2026-40814. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-40814 affect?
CVE-2026-40814 affects Web app containing dataapi.php; function _mb24confi_getTagAlarm. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-40814?
Patch when available; enforce input validation and WAF.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated SQLi allows data exfiltration; total loss of confidentiality.
Immediate action required
- affected<= 2.20.0
- affected2.20.0
- affected<= 2.20.0
- affected2.20.0
- affected<= 2.20.0
- affected2.20.0
- affected<= 2.20.0
- affected2.20.0
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.