CVE-2026-14238: vitepos (WordPress plugin) · SQL Injection
Affects vitepos (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 4.1 Medium : upgrade to 3.6.0 when convenient.
Data as of 7 Nov 2026, 23:24 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.6.0
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.
What to do
Upgrade vitepos (WordPress plugin) to 3.6.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| vitepos | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, restrict administrator access to trusted users only and monitor for suspicious activity related to the vitepos plugin. Avoid exposing the vulnerable report endpoints unnecessarily.
Description
The vitepos WordPress plugin before 3.6.0 does not sanitize or parameterize an identifier taken from a REST request body before using it in a database query in one of its report endpoints, allowing users with administrator-level access to perform SQL injection.