CVE-2026-3334

The CMS Commander plugin for WordPress is vulnerable to SQL Injection via the 'or_blogname', 'or_blogdescription', and 'or_admin_email' parameters in all versions up to, and including, 2.

Verified by Precogs Threat Research
Last Updated: Mar 21, 2026
Base Score
8.8HIGH

Executive Summary

CVE-2026-3334 is a high severity vulnerability affecting appsec, ai-code, pii-secrets. It is classified as SQL Injection. Ensure your systems and dependencies are patched immediately to mitigate exposure risks.

Precogs AI Insight

"The root cause of this vulnerability lies in within The CMS Commander plugin, allowing bypassed validation checks on external interactions. By manipulating this weakness, a threat actor can gain unauthorized read or write access, effectively hijacking underlying configurations. Precogs identifies insecure data flow paths before deployment to alert security teams to imminent boundary violations."

Exploit Probability (EPSS)
Low (0.0%)
Public POC
Undisclosed
Exploit Probability
Elevated (52%)
Public POC
Available
Affected Assets
appsecai codepii secretsCWE-89

What is this vulnerability?

CVE-2026-3334 is categorized as a critical SQL Injection flaw. Based on our vulnerability intelligence, this issue occurs when the application fails to securely handle untrusted data boundaries.

The CMS Commander plugin for WordPress is vulnerable to SQL Injection via the 'or_blogname', 'or_blogdescription', and 'or_admin_email' parameters in all v...

This architectural defect enables adversaries to bypass intended security controls, directly manipulating the application's execution state or data layer. Immediate strategic intervention is required.

Risk Assessment

MetricValue
CVSS Base Score8.8 (HIGH)
Vector StringCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
PublishedMarch 21, 2026
Last ModifiedMarch 21, 2026
Related CWEsCWE-89

Impact on Systems

Data Exfiltration: Full compromise of the database schema, allowing extraction of all tables, user records, and PII.

Authentication Bypass: Attackers can manipulate boolean logic in authentication queries to log in as administrators.

Remote Code Execution: In severe configurations (e.g., xp_cmdshell in MSSQL), attackers can execute shell commands on the database underlying OS.

How to fix this issue?

Implement the following strategic mitigations immediately to eliminate the attack surface.

1. Prepared Statements Migrate entirely to parameterized queries (Prepared Statements) or an Object-Relational Mapper (ORM) to decouple code from data.

2. Input Validation Implement rigorous allow-list input validation for all sorting, filtering, and query parameters.

3. Principle of Least Privilege Ensure the database service account has the minimum necessary privileges, restricting DROP, TRUNCATE, and system execution commands.

Vulnerability Signature

// Example of a vulnerable Node.js/Express snippet

const category = req.query.category;

// DANGEROUS: Direct string concatenation of user input
const query = `SELECT * FROM products WHERE category = '$\{category\}'`;

db.query(query, (err, result) =\> \{
  if (err) throw err;
  console.log(result);
\});

// SECURED: Using parameterized queries avoids SQL injection
const category = req.query.category; // Ensure scope appropriately

// Safe: The database driver treats '?' strictly as data, not executable code
const query = 'SELECT * FROM products WHERE category = ?';

db.query(query, [category], (err, result) =\> \{
  if (err) throw err;
  console.log(result);
\});

References and Sources

Vulnerability Code Signature

Attack Data Flow

StageDetail
SourceUser-controlled HTTP request parameter
VectorString concatenation into SQL query string
SinkDatabase engine executes the malformed query
ImpactFull database compromise, unauthorized data modification or exfiltration

Vulnerable Code Pattern

# ❌ VULNERABLE: Direct string concatenation
def get_user(user_id):
    query = "SELECT * FROM users WHERE id = '" + user_id + "'"
    cursor.execute(query)  # Taint sink: unparameterized query
    return cursor.fetchone()

Secure Code Pattern

# ✅ SECURE: Parameterized query
def get_user(user_id):
    query = "SELECT * FROM users WHERE id = %s"
    cursor.execute(query, (user_id,))  # Sanitized binding
    return cursor.fetchone()

How Precogs Detects This

Precogs AI Analysis Engine traces data flow from HTTP request parameters through string concatenation directly into database execution sinks, identifying critical SQL injection vectors via Code Property Graph traversal.\n

Related Vulnerabilitiesvia CWE-89

Is your system affected?

Precogs AI detects CVE-2026-3334 in compiled binaries, LLMs, and application layers — even without source code access.