WordPress Question Answer Plugin SQL Injection via Unescaped Input

The PickPlugins Question Answer plugin for WordPress is vulnerable to SQL Injection in versions up to and including 1.2.73. This is due to insufficient sanitization of user-supplied input via the 'id' GET parameter in the user profile template combined with the use of wp_unslash() which removes WordPress's magic quotes protection, followed by direct concatenation into a SQL query without proper escaping or prepared statements in the qa_user_profile_card() function. This makes it possible for unauthenticated attackers to append additional SQL queries into existing queries, which can be used to extract sensitive information from the database.

Casky was already ahead

This CVE exploits attack patterns that Casky's 322matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

The PickPlugins Question Answer plugin for WordPress contains a critical SQL injection vulnerability in versions through 1.2.73, stemming from inadequate input sanitization in the qa_user_profile_card() function. The vulnerability exploits the 'id' GET parameter, which is processed through wp_unslash() to remove WordPress security protections, then directly concatenated into SQL queries without prepared statements or proper escaping. This allows unauthenticated attackers to inject malicious SQL commands, potentially extracting sensitive data, modifying database contents, or escalating privileges. Any WordPress installation running the vulnerable plugin version exposes its entire database to compromise, making this a high-severity threat affecting site administrators and users whose data is stored in affected instances.

Casky's 322 matched skills leverage Claude's extended reasoning to correlate this vulnerability with MITRE ATT&CK techniques TA0001 (Initial Access) and TA0043 (Reconnaissance). Practitioners using Casky would identify attack patterns including: suspicious GET parameter manipulation attempts (CWE-89 exploitation signatures), abnormal SQL query structures in web logs, and database access anomalies indicative of data exfiltration. The platform's skills would highlight the specific attack chain—parameter injection → wp_unslash() bypass → unescaped query execution—enabling defenders to detect similar exploitation attempts across their WordPress infrastructure, validate patch deployment for version 1.2.74+, and hunt for indicators of prior exploitation in access logs and database audit trails.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

322 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-10207.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-10207

Casky has 322 skills that investigate the attack patterns behind CVE-2026-10207. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn