Security readout for executives and security teams
Plain-English summary
Directory Pro for WordPress versions through 2.5.8 reportedly allow unauthenticated attackers to inject database queries remotely. Successful exploitation could expose sensitive database information and cause limited service disruption. The supplied record rates it critical, but provides no evidence of active exploitation or a confirmed fixed version.
Executive priority
Treat this as an urgent exposure-validation and remediation task because exploitation requires no account and could disclose sensitive database information. Prioritize public WordPress sites. Do not describe it as actively exploited based on the supplied evidence; first establish whether Directory Pro 2.5.8 or earlier is present.
Technical view
CVE-2026-66649 is classified as CWE-89 SQL injection with CVSS 3.1 score 9.3. The vector indicates network access, low complexity, no privileges, and no user interaction, with high confidentiality and low availability impact. The bundle does not identify the vulnerable parameter, request path, root cause, or remediation release.
Likely exposure
Internet-accessible WordPress sites running Directory Pro 2.5.8 or earlier are the likely exposure population. Actual exposure depends on whether the vulnerable plugin functionality is installed and reachable. The structured affected-product entry is incomplete and conflicting: versions are listed as “n/a” while its default status says unaffected.
Exploitation context
The vulnerability is described as remotely exploitable without authentication, privileges, or user interaction. However, the source bundle marks it absent from KEV and supplies no evidence of exploitation in the wild, public proof-of-concept availability, or attacker campaigns. Exploitation status should therefore be treated as unconfirmed.
Researcher notes
The public bundle supports the SQL-injection classification, affected-version ceiling, and CVSS vector, but lacks endpoint-level details, technical analysis, exploit artifacts, and a named fixed version. The affected array’s “n/a” versions and default-unaffected status conflict with the title and description, so authoritative vendor or Patchstack confirmation is important.
Mitigation direction
- Inventory WordPress sites for Directory Pro and record installed versions.
- Prioritize sites running Directory Pro 2.5.8 or earlier.
- Check Patchstack and vendor guidance for a confirmed fixed release or mitigation.
- Apply the confirmed vendor update after testing and back up the site first.
- Consider disabling the plugin until remediation if business operations permit.
Validation and detection
- Confirm the plugin version from trusted WordPress administration or asset records.
- Verify whether affected plugin functionality is reachable from unauthenticated networks.
- Review web and database logs for anomalous requests or query-related errors.
- Confirm the deployed version against current vendor or Patchstack guidance.
- Retest normal site behavior after updating or disabling the plugin.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-66649 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L3.94.7PatchstackVulnerability scoring details
Base CVSS 3.1 score
9.3CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/wordpress/plugin/directory-pro/vulnerability/wordpress-directory-pro-plugin-2-5-8-sql-injection-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command
Improper Neutralization of Special Elements used in an SQL Command represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.