# CVE-2026-27743: SPIP referer_spam < 1.3.0 Unauthenticated SQL Injection

> Unauthenticated attackers can execute arbitrary SQL queries via the url parameter in the referer_spam plugin, leading to data exposure or modification.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Feb 2026
- **Updated:** 25 May 2026
- **Also known as:** GHSA-pg8p-25c5-3f44

## What is CVE-2026-27743?

CVE-2026-27743 is a critical SQL injection vulnerability in SPIP referer_spam, published on 25 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The SPIP referer_spam plugin versions prior to 1.3.0 contain an unauthenticated SQL injection vulnerability in the referer_spam_ajouter and referer_spam_supprimer action handlers. The handlers read the url parameter from a GET request and interpolate it directly into SQL LIKE clauses without input validation or parameterization. The endpoints do not enforce authorization checks and do not use SPIP action protections such as securiser_action(), allowing remote attackers to execute arbitrary SQL queries.

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

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

It affects 1 product.


Products: Spip Referer Spam.

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

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

## Is CVE-2026-27743 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-27743 is a critical SQL injection vulnerability in SPIP referer_spam, published on 25 Feb 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-27743 exists.

Affected product: SPIP referer_spam. 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-27743/ (Markdown: https://insights.sbomify.com/CVE-2026-27743/index.md)
```

## Sources

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

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