Home › Intelligence › Brief
VULNERABILITY BRIEF 🟠 High Vulnerability

Critical SQL Injection (CVE-2026-2413) in Ally WordPress Plugin Threatens 400,000+ Sites

A newly disclosed unauthenticated SQL injection (CVE‑2026‑2413) in the Ally accessibility plugin affects over 400,000 WordPress sites. Attackers can extract password hashes and other sensitive data, creating a significant third‑party risk for organizations that host or rely on WordPress‑based services.

Verisq™ Intelligence · 📅 March 14, 2026 · 📰 securityaffairs.com
🟠
Severity
High
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
2 sector(s)
✅
Actions
5 recommended
📰
Source
securityaffairs.com

Critical SQL Injection (CVE‑2026‑2413) in Ally WordPress Plugin Threatens 400,000+ Sites

What It Is — The Ally accessibility plugin for WordPress (formerly One Click Accessibility) contains an unauthenticated SQL‑injection flaw (CVE‑2026‑2413). By supplying a crafted URL parameter, an attacker can inject arbitrary SQL into a JOIN clause and retrieve sensitive database records, including password hashes. All versions up to 4.0.3 are vulnerable.

Exploitability — The vulnerability is publicly disclosed, a proof‑of‑concept (time‑based blind injection) has been released, and it carries a CVSS v3.1 score of 7.5 (High). No widespread ransomware‑style campaigns have been observed yet, but exploitation requires only network access and no authentication.

Affected Products — Ally (One Click Accessibility) WordPress plugin, versions ≤ 4.0.3; estimated > 400,000 WordPress sites worldwide.

TPRM Impact —

  • Large supply‑chain exposure: any organization that hosts client‑facing WordPress sites or relies on third‑party WordPress implementations inherits this risk.
  • Potential credential theft and data leakage across multiple industries, increasing downstream breach liability.
  • May affect SaaS platforms that embed WordPress as a content engine, amplifying the attack surface.

Recommended Actions —

  1. Inventory all WordPress installations and identify sites running the Ally plugin.
  2. Patch immediately to Ally 4.1.0 (or later) – the only version that mitigates the flaw.
  3. Validate that the update is applied via automated configuration management tools.
  4. Run a database integrity check for unexpected modifications or extracted data.
  5. Deploy WAF rules to block suspicious URL patterns targeting the vulnerable endpoint.
  6. Update third‑party risk registers to flag Ally as a high‑severity finding and require remediation in vendor contracts.

Source: Security Affairs

📰 Original Source
https://securityaffairs.com/189354/security/critical-sql-injection-bug-in-ally-plugin-threatens-400000-wordpress-sites.html ↗

This Verisq Intelligence Brief is an independent analysis. Read the original reporting at the link above.

Vulnerability exposure

Is this CVE in your supply chain?

Verisq matches published vulnerabilities against the software your vendors run, so you know which relationships this touches before the next review.

See vendor exposure →