# CVE-2026-2413: Ally – Web Accessibility & Usability <= 4.0.3 - Unauthenticated SQL Injection via URL Path

> Unauthenticated attackers can extract sensitive database information via SQL injection in the Ally WordPress plugin when the Remediation module is active.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Mar 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-83wr-6xhc-8r8r

## What is CVE-2026-2413?

CVE-2026-2413 is a high-severity SQL injection vulnerability in elemntor Ally – Web Accessibility & Usability, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Ally – Web Accessibility & Usability plugin for WordPress is vulnerable to SQL Injection via the URL path in all versions up to, and including, 4.0.3. This is due to insufficient escaping on the user-supplied URL parameter in the `get_global_remediations()` method, where it is directly concatenated into an SQL JOIN clause without proper sanitization for SQL context. While `esc_url_raw()` is applied for URL safety, it does not prevent SQL metacharacters (single quotes, parentheses) from being injected. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database via time-based blind SQL injection techniques. The Remediation module must be active, which requires the plugin to be connected to an Elementor account.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-2413?


## How do I fix CVE-2026-2413?

No fix has been published for CVE-2026-2413 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-2413 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2413 exists.

Public exploit code:

- https://github.com/p3Nt3st3r-sTAr/CVE-2026-2413-POC (github_poc): https://github.com/p3Nt3st3r-sTAr/CVE-2026-2413-POC
- Ally – Web Accessibility & Usability <= 4.0.3 - Unauthenticated SQL Injection via URL Path (github_poc): https://github.com/RandomRobbieBF/CVE-2026-2413
- Ally – Web Accessibility & Usability <= 4.0.3 - SQL Injection (nuclei): http/cves/2026/CVE-2026-2413.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2413 and fix it if it is affected.

What it is: CVE-2026-2413 is a high-severity SQL injection vulnerability in elemntor Ally – Web Accessibility & Usability, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2413 exists.

Affected product: elemntor Ally – Web Accessibility & Usability. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-2413/ (Markdown: https://insights.sbomify.com/CVE-2026-2413/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2413
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2413
- OSV: https://osv.dev/vulnerability/CVE-2026-2413

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-2413/
Summaries are generated and may contain mistakes; the official description above is the record.