Security readout for executives and security teams
Plain-English summary
A Grav CMS database plugin flaw lets unsafe table names reach a raw SQL query in PDO::tableExists(). If another plugin or custom code passes attacker-controlled table names into that method, attackers may run arbitrary SQL against the configured database. The source says version 1.2.0 fixes it.
Executive priority
Treat as urgent for Grav environments using the database plugin, especially sites with custom plugins. The impact can include database confidentiality and integrity compromise, but exposure depends on application-specific code paths. Prioritize upgrade and code review.
Technical view
Before 1.2.0, grav-plugin-database interpolates the table argument directly into SQL without sanitization, escaping, quoting, or whitelisting. The weakness is SQL injection, CWE-89, with CVSS 4.0 score 9.2. Exploitability depends on consuming plugin or developer code exposing attacker-controlled table names.
Likely exposure
Exposure is likely limited to Grav installations using grav-plugin-database before 1.2.0 where custom or third-party code calls PDO::tableExists() with attacker-influenced input. The provided sources do not prove all Grav sites are affected.
Exploitation context
The bundle reports KEV status as false and provides no evidence of active exploitation. The flaw is network-reachable in scoring, but requires a vulnerable application code path that passes attacker-controlled table names into the affected method.
Researcher notes
The key constraint is attack surface: the vulnerable method exists in the plugin, but exploitation requires attacker-controlled table names reaching PDO::tableExists(). Sources identify the fix commit and 1.2.0 release, but do not include exploit telemetry or broader product impact evidence.
Mitigation direction
- Upgrade grav-plugin-database to version 1.2.0 or later.
- Review vendor advisory and release notes before production rollout.
- Audit custom and third-party Grav code using PDO::tableExists().
- Prevent untrusted input from controlling database table names.
- Check vendor guidance if immediate upgrade is not possible.
Validation and detection
- Inventory Grav sites using grav-plugin-database.
- Confirm installed plugin version is 1.2.0 or later.
- Search application code for calls to PDO::tableExists().
- Trace whether table names can originate from user-controlled input.
- Review database access logs for suspicious errors or unexpected queries.
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-58492 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.2 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA: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.
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:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
9.2CriticalVector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N
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://github.com/getgrav/grav/security/advisories/GHSA-8jxg-4pw9-xcwfCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/getgrav/grav-plugin-database/commit/f6d058785c9e23df7efc5ea7556f8746fef286dfCVE reference, GitHub_M · x_refsource_MISC
- https://github.com/getgrav/grav-plugin-database/releases/tag/1.2.0CVE reference, GitHub_M · x_refsource_MISC
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.