Security readout for executives and security teams
Plain-English summary
Everest Backup versions 2.3.12 and earlier contain a critical database-injection flaw reachable without authentication. A remote attacker could potentially access sensitive WordPress database information and cause limited service disruption. The supplied sources do not identify a fixed version or confirm active exploitation.
Executive priority
Treat as an urgent remediation item for public WordPress systems. Prioritize discovery immediately, reduce exposure, and obtain verified vendor remediation guidance before relying on an upgrade.
Technical view
CVE-2026-66472 is an unauthenticated SQL injection vulnerability classified as CWE-89. Its CVSS 3.1 score is 9.3, with network access, low complexity, no privileges, no user interaction, changed scope, high confidentiality impact, no integrity impact, and low availability impact. The vulnerable endpoint and injection mechanism are not described.
Likely exposure
Likely exposure exists where Everest Backup version 2.3.12 or earlier is installed on an internet-reachable WordPress site. No account or user interaction is reportedly required. Exact configuration prerequisites and vulnerable request paths are not supplied.
Exploitation context
The CVE is not listed as KEV in the supplied bundle, and no cited source confirms exploitation in the wild. No public proof of concept is identified here. This absence does not establish that exploitation is impossible or has not occurred.
Researcher notes
Evidence is limited to the CVE metadata and Patchstack entry. The bundle states versions through 2.3.12 are vulnerable, while its structured affected entry says version “n/a” with default status “unaffected.” Treat the explicit description as the exposure lead, but verify product-version applicability independently. No endpoint, root cause, patch version, or exploit evidence is provided.
Mitigation direction
- Inventory WordPress sites for Everest Backup and record each installed version.
- Check vendor and Patchstack guidance for a fixed release; none is identified in the supplied sources.
- Until remediated, disable the affected plugin where business operations permit.
- Restrict public access and monitor database-facing activity as temporary compensating controls.
Validation and detection
- Confirm whether Everest Backup is installed, including inactive copies and deployment artifacts.
- Verify that no installed instance is version 2.3.12 or earlier.
- Review web, application, and database logs for unusual unauthenticated requests or query errors.
- Confirm remediation against current vendor guidance before restoring normal exposure.
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-66472 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/everest-backup/vulnerability/wordpress-everest-backup-plugin-2-3-12-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 ('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.