CVE-2026-66649
Unauthenticated SQL injection in Directory Pro ≤2.5.8 enabling DB compromise.
Is CVE-2026-66649 being exploited?
Not confirmed. CVE-2026-66649 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.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-66649?
CVE-2026-66649 is rated Critical with a CVSS score of 9.3. 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-66649?
Not known from our data. No patch reference has been recorded for CVE-2026-66649, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-66649 affect?
CVE-2026-66649 affects Directory Pro <= 2.5.8, Web applications using Directory Pro. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-66649?
Apply vendor patch when available; block public access, add WAF rules, rotate DB creds, audit logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated SQLi allows attackers to read/modify/delete database records, bypass auth, exfiltrate data, and potentially pivot to RCE.
Immediate action required
- affected<= 2.5.8
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.