Skip to main content

Affiliate Toolkit CVE-2026-42721

| EUVDEUVD-2026-94262 HIGH
SQL Injection (CWE-89)
2026-10-07 Patchstack GHSA-m2c3-6qqh-2gh9
7.6
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as high-privilege WordPress user
  2. Delivery
    Submit crafted input to vulnerable plugin parameter
  3. Exploit
    Trigger blind SQL injection in query
  4. Execution
    Infer data via boolean/time responses
  5. Impact
    Exfiltrate sensitive database contents

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires an authenticated session with high privileges (administrator-level, per PR:H in the CVSS vector) on a WordPress site running the affiliate-toolkit / affiliate-toolkit-starter plugin at version 3.9.1 or earlier; the attacker then supplies malicious input to a plugin parameter that is concatenated into a SQL query. Key limiting factors: the high-privilege authentication requirement excludes anonymous and low-privilege users, and the injection is blind (no direct query output), so data must be extracted via inference. Exploitation is remote over the network with low complexity and no user interaction once that privileged access exists.

Impact

This is a moderate-priority issue rather than an emergency. The CVSS 3.1 base score of 7.6 (vector AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L) is driven largely by the Scope:Changed flag and network reachability, but the single most important mitigating signal is PR:H - exploitation requires an already-authenticated high-privilege account (typically administrator-level on the WordPress site), which sharply narrows the realistic attacker population. No EPSS score, no CISA KEV listing, and no public proof-of-concept were provided in the input, so there is no evidence of active exploitation or automation: exploitation status is 'no public exploit identified at time of analysis.' The blind nature of the SQL injection also raises the operational effort required, since data must be inferred boolean/time-wise rather than read directly. One signal worth flagging: Patchstack's assignment of S:C (scope change) and A:L for a blind SQL injection is atypical and inflates the score somewhat - a more conventional assessment would treat this as S:U with confidentiality-only impact. Net: a genuine vulnerability that authenticated-admin threat models should patch, but not a mass-exploitation / drop-everything priority given PR:H and the absence of KEV/POC/EPSS signals.

Exploit ScenarioDerived

An attacker who has already obtained a high-privilege (administrator-level) account on a WordPress site running affiliate-toolkit 3.9.1 or earlier submits crafted input to a vulnerable plugin parameter, triggering a blind SQL injection. Because the injection is blind, the attacker uses boolean- or time-based inference to extract sensitive database contents such as user records and credentials. No public exploit code was identified at the time of analysis, and the PR:H requirement means a privileged foothold is a prerequisite.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 07, 2026

Blind SQL injection in the WordPress plugin affiliate-toolkit (a.k.a. affiliate-toolkit-starter) through version 3.9.1 lets an attacker with an authenticated, high-privilege (administrator-level) account inject arbitrary SQL into plugin queries and exfiltrate database contents through inference-based techniques. The attack is remote, low complexity, and requires no victim interaction once that privileged session exists, but the administrator-level prerequisite (PR:H) sharply limits the realistic attacker pool, and because the injection is blind, exploitation is slower and noisier than a direct-output SQLi. Per our independent assessment this is a moderate-priority issue rather than an emergency; no public exploit identified at time of analysis, and no CISA KEV listing applies.

RemediationAI

No vendor-released patch was identified at time of analysis, so the immediate priorities are containment and monitoring rather than applying a fixed version. Track the affiliate-toolkit / affiliate-toolkit-starter plugin page and the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/affiliate-toolkit-starter/vulnerability/wordpress-affiliate-toolkit-plugin-3-9-1-sql-injection-vulnerability?_s_id=cve for a fixed release and upgrade the moment one ships - do not treat 3.9.1 as safe. If the plugin's affiliate-toolkit functionality is not in active use, deactivate and delete it, which removes the exposure entirely at the cost of losing affiliate feed and link-manager features. Because exploitation requires an administrator-level session, harden that layer: enforce unique credentials and MFA for every administrator, audit and prune stale or overly broad admin accounts, and restrict wp-admin and wp-login.php access by IP allowlist or a Zero Trust/VPN front end - accepting that this breaks administrative access from unlisted networks and from mobile or on-the-go admins. Deploy a WAF or reverse-proxy rule set that flags SQL metacharacters (UNION, SLEEP, BENCHMARK, stacked queries, boolean predicates) in requests touching affiliate-toolkit endpoints; be aware that generic SQLi rules generate false positives on legitimate search or filter traffic, so start in detection-only mode and tune before blocking. Enable database and web-server query logging for the plugin's parameters and alert on SLEEP/BENCHMARK-style timing probes, which are the most common fingerprint of blind exploitation. As a last resort in high-sensitivity environments, migrate the affiliate data to a separate database user with read/write privileges limited to the plugin's own tables so a successful injection cannot reach wp_users or other core WordPress secrets - this requires schema and configuration changes and will break plugins that expect shared credentials.

Affected VersionsENISA

affiliate-toolkit 0 ≤3.9.1

Affected Packages

euvd affiliate_toolkit no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is a classic CWE-89 improper neutralization of special elements in an SQL command, rooted in the affiliate-toolkit WordPress plugin (CPE cpe:2.3:a:servit_software_solutions:affiliate-toolkit:*:*:*:*:*:*:*:*, vendor SERVIT Software Solutions), a PHP plugin that manages affiliate links, product feeds, and related marketing data inside the WordPress database. A plugin parameter is concatenated into a SQL statement without proper parameterization or escaping, so an authenticated caller can append SQL syntax that alters the query's logic. The advisory classifies the result as blind SQL injection, meaning the application does not return query results or errors directly; an attacker must instead infer data bit-by-bit using boolean- or time-based payloads against the underlying MySQL/MariaDB backend. The published CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L) and our independent assessment (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N) agree on the essentials: network-reachable, low complexity, high-privilege authenticated, no user interaction, with confidentiality as the dominant impact; the two differ on scope and on whether limited integrity/availability effects exist, and we treat the confidentiality-only, scope-unchanged view as the authoritative characterization.

Know when Affiliate Toolkit gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 7.6 HIGH
AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L
vuln.today AI 4.9 MEDIUM

Remote low-complexity injection but needs admin-level access (PR:H); blind SQLi primarily enables data disclosure (C:H), with no demonstrated integrity/availability impact or cross-component scope change (S:U).

3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

DescriptionCVE.org

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in SERVIT Software Solutions affiliate-toolkit affiliate-toolkit-starter allows Blind SQL Injection.This issue affects affiliate-toolkit: from n/a through 3.9.1.

Executive ViewAI

Why It Matters

The affiliate-toolkit plugin for WordPress (through version 3.9.1) has a blind SQL injection vulnerability that requires an administrator-level account to exploit. This prerequisite significantly limits the attacker pool, but if an administrative account is compromised, sensitive data could be exfiltrated, impacting customer trust and compliance. Since no vendor patch is available, leadership should ensure interim mitigations are in place to reduce risk.

Business Impact: Medium
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: disable the affiliate-toolkit plugin until a patch is available; if the plugin must remain active, restrict administrator access to trusted networks, enforce multi-factor authentication, implement a web application firewall with SQL injection rules, and monitor database queries for suspicious activity.

Threat Intelligence Overview

EPSS Score
0.4%
Top 70% exploitable
Prevalence
Low
niche affiliate-marketing WordPress plugin, modest install base
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
Medium
Technical Impact
Partial

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy