Security readout for executives and security teams
Plain-English summary
CVE-2026-2576 affects the Business Directory Plugin for WordPress. An unauthenticated attacker may be able to extract sensitive database information through a vulnerable payment parameter. This is a confidentiality-focused issue with high severity. Public sources do not show confirmed active exploitation, and the affected-version wording is inconsistent.
Executive priority
Prioritize remediation for public WordPress sites using this plugin. The business risk is potential database information disclosure without login. Move quickly, but do not assume active exploitation unless new trusted sources confirm it.
Technical view
The CVE describes a time-based SQL injection in the payment parameter caused by insufficient escaping and query preparation. It is categorized as CWE-89 with CVSS 3.1 score 7.5, network exploitable, low complexity, no authentication, and no user interaction. References point to checkout handling and query-set code, plus a WordPress Trac changeset.
Likely exposure
WordPress sites running Business Directory Plugin may be exposed, especially if using versions covered by the CVE. The title says <= 6.4.21, while the description says <= 6.4.2. Treat 6.4.21 and earlier as potentially affected until vendor guidance confirms scope.
Exploitation context
No CISA KEV listing or provided source confirms active exploitation. The issue is still serious because it is unauthenticated, remotely reachable, and targets database confidentiality. Time-based SQL injection can be slower but may still enable sensitive data extraction.
Researcher notes
Version scope is inconsistent between the title and description, so validation should document both interpretations. The referenced Trac changeset is relevant for remediation review. Avoid relying only on scanner labels until vendor or Wordfence confirms the exact fixed version.
Mitigation direction
- Inventory all WordPress sites using Business Directory Plugin.
- Check vendor or WordPress plugin guidance for the fixed release.
- Update to the release containing the referenced Trac fix when available.
- Use WAF rules to reduce suspicious payment parameter traffic.
- Restrict unnecessary public access to affected checkout flows where feasible.
Validation and detection
- Confirm installed Business Directory Plugin versions across all WordPress environments.
- Treat 6.4.21 and earlier as potentially affected pending clarification.
- Review web and WAF logs for unusual payment parameter requests.
- Verify the referenced code changes are present after updating.
- Monitor Wordfence and CVE records for affected-version clarification.
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-2576 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
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
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:U/C:H/I:N/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/d8ec7d25-1574-416c-b5fd-3a71b1cc09d2?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/business-directory-plugin/tags/6.4.21/includes/db/class-db-query-set.php#L37CVE reference
- https://plugins.trac.wordpress.org/browser/business-directory-plugin/tags/6.4.21/includes/controllers/pages/class-checkout.php#L126CVE reference
- https://plugins.trac.wordpress.org/changeset/3463307/business-directory-plugin/trunk/includes/db/class-db-query-set.phpCVE reference
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 ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.