CVE-2023-6063
SQLi in Wpfastestcache Wp Fastest Cache ≤ 1.2.2
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-6063 is a high-severity SQL Injection (CWE-89) vulnerability in Wpfastestcache Wp Fastest Cache. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Protocol or Service Impersonation (T1001.003); ranked in the top 0.5% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
The vulnerability CVE-2023-6063 is an unauthenticated SQL injection flaw present in the WP Fastest Cache WordPress plugin prior to version 1.2.2. It arises because the plugin fails to properly sanitize and escape a parameter before incorporating it into a SQL statement, corresponding to CWE-89 and carrying a CVSS 3.1 score of 7.5 that reflects high confidentiality impact over a network vector with no required privileges or user interaction.
An attacker with no authentication can supply a crafted parameter to the affected plugin endpoint, enabling direct execution of arbitrary SQL queries against the underlying database and potential extraction of sensitive data such as user credentials or site configuration.
Public advisories published by WPScan state that the flaw was resolved in plugin release 1.2.2 and explicitly advise site administrators to update immediately to eliminate the injection vector.
The associated EPSS reaches a current value of 0.9137 with a recorded peak of 0.9221, indicating sustained and elevated exploitation interest following disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-58320
Vulnerability Data
The WP Fastest Cache WordPress plugin before 1.2.2 does not properly sanitise and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by unauthenticated users.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.2.5
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly target injection flaws during coding and review so largely prevent CWE-89 introduction, yet the single broad outcome leaves residual risk from incomplete neutralization techniques or missed edge cases.
Training raises developer awareness of SQLi risks and can reduce introduction likelihood (partial) but removes none of the actual coding flaw's risk by itself since technical neutralization is still required.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
A.5.6 only improves knowledge flow, awareness of threats/patches and access to specialist advice; it does not stop SQL injection from being exploitable in code that still contains the flaw.