Security readout for executives and security teams
Plain-English summary
Public-facing WordPress sites using Beautiful Taxonomy Filters version 2.4.6 or earlier may let an unauthenticated attacker manipulate database queries. The reported impact is primarily serious data exposure, with some potential service disruption. No user interaction or account is required.
Executive priority
Treat as an immediate inventory and remediation priority for internet-facing WordPress systems. Prioritize sites holding sensitive customer, employee, or operational data. If no confirmed fixed release exists, evaluate disabling the plugin while preserving required business functionality.
Technical view
CVE-2026-78288 is a CWE-89 SQL injection affecting Beautiful Taxonomy Filters through version 2.4.6. CVSS 3.1 rates it 9.3: network-accessible, low complexity, unauthenticated, and requiring no user interaction. The supplied sources do not identify the vulnerable parameter, reachable route, patch version, or precise database access.
Likely exposure
Exposure is likely where the WordPress plugin is installed, enabled, version 2.4.6 or earlier, and its vulnerable functionality is internet-accessible. Sites without the plugin, or with versions confirmed unaffected by authoritative vendor guidance, are not established as exposed by this bundle.
Exploitation context
The CVSS vector indicates remote, low-complexity exploitation without authentication or user interaction. However, the CVE is not listed as KEV in the supplied bundle, and no cited source establishes active exploitation, public proof-of-concept availability, or exploitation prevalence.
Researcher notes
The supplied record supports unauthenticated SQL injection and the affected upper bound, but lacks parameter, endpoint, root-cause, patch, and observed-exploitation details. The structured affected entry also says versions are unavailable and defaults to unaffected, creating ambiguity. Validate against current authoritative advisories before making final exposure determinations.
Mitigation direction
- Inventory all WordPress sites for Beautiful Taxonomy Filters and record installed versions.
- Check Patchstack and authoritative vendor guidance for a fixed release or approved mitigation.
- Update to a confirmed fixed version when one is identified.
- Disable or remove the plugin if no confirmed fix is available and business operations permit.
- Restrict unnecessary public access and monitor database and web logs for anomalies.
Validation and detection
- Confirm whether Beautiful Taxonomy Filters is installed and enabled on every WordPress instance.
- Verify the deployed plugin version using trusted administrative inventory.
- Compare versions against the affected range of 2.4.6 and earlier.
- Review vendor guidance to confirm whether the installed release is fixed.
- Inspect web and database logs for unusual requests or query errors without attempting exploitation.
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-78288 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
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.