myCred blind SQL injection in plugin database queries
- Exploited
- No known exploitation
- Fix
- Fixed in 4.0.3
- Who is exposed
- Specific setups only
Summary
Vendor myCred's myCred plugin for WordPress contains an SQL injection flaw that lets an attacker run blind SQL queries against the database. The attacker can reach it remotely over the network, but needs a low-privilege login first.
Written by a model
Original description
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in myCred myCred mycred allows Blind SQL Injection.This issue affects myCred: from n/a through 4.0.2.
What to do
Upgrade to a fixed version: 4.0.3.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-125811 (WordPress myCred plugin <= 4.0.2 - SQL Injection vulnerability), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-125811 (entry last updated 2026-11-13):
Affected:
- myCred myCred: fixed in 4.0.3
Fixed versions: 4.0.3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-125811 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125811 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/mycred/vulnerability/wordpress-mycred-plugin-4-0-2-sql-injection-vulnerability?_s_id=cve
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-125811
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-125811"}.Affected versions
- mycredfixed in 4.0.3 · through 4.0.2
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.5/10CVSS 8.5
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Public exploit activity
- EPSS: 0.33%
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-125811 |
| Record | NVD · CVE-2026-125811 |
| Other links 1 | |
| Link | patchstack.com · database/wordpress/plugin/mycred/vulnerability/wordpress-mycred-plugin-4-0-2-sql-injection-vulnerability?_s_id=cve |
Questions about CVE-2026-125811
Is CVE-2026-125811 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
The SQL injection flaw lets an attacker read, modify, or delete the entire site database, including user accounts and private data.
Source: patchstack.com
Which versions are affected by CVE-2026-125811?
mycred: through 4.0.2 (fixed in 4.0.3).
Source: cve.now feed data
Am I affected, and how do I check?
The myCred plugin for WordPress, versions up to and including 4.0.2. The installed version is shown on the Plugins page in the WordPress admin, where the myCred entry lists its version number.
Source: patchstack.com
How do I fix CVE-2026-125811?
Update the myCred plugin to version 4.0.3 or later.
Source: patchstack.com
Related
- CVE-2026-123465WordPress myCred plugin <= 4.0.2 - Sensitive Data Exposure vulnerability
- CVE-2026-125809WordPress myCred plugin <= 4.0.2 - Cross Site Scripting (XSS) vulnerability
- CVE-2026-56013WordPress License Manager for WooCommerce plugin <= 3.0.15 - Insecure Direct Object References (IDOR) vulnerability
- CVE-2026-40794WordPress myCred plugin <= 3.0.3 - Broken Access Control vulnerability
- CVE-2025-69332WordPress Bookify plugin <= 1.1.1 - Broken Access Control vulnerability
- CVE-2026-42676WordPress myCred plugin <= 3.0.4 - Cross Site Scripting (XSS) vulnerability
No corrections so far. Something wrong on this page? Report an error.