CVE-2026-27743
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe SPIP referer_spam plugin versions before 1.3.0 contain an unauthenticated SQL injection vulnerability in the referer_spam_ajouter and referer_spam_supprimer action handlers. The url parameter from GET requests is directly interpolated into SQL LIKE clauses without input validation or parameterized queries, and no authorization checks or securiser_action() protections are implemented, allowing remote attackers to execute arbitrary SQL queries.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.3.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the referer_spam plugin installationCheck your SPIP installation's /plugins/ or /plugins-dist/ directory for a folder named 'referer_spam' or similar. Also check the SPIP plugin management interface for installed plugins.Affected if The referer_spam plugin is not found in the expected plugin directories.
-
Determine the installed plugin versionInspect the plugin's packaging.xml, plugin.xml, or info.xml file within the referer_spam plugin directory to read the version number.Affected if The version listed is less than 1.3.0 (for example: 1.2.x, 1.1.x, or any version before 1.3.0).
-
Identify vulnerable action filesLook for files named referer_spam_ajouter.php and/or referer_spam_supprimer.php in the plugin's action or includes subdirectory.Affected if These action handler files exist in the plugin directory.
-
Inspect the url parameter handling in vulnerable actionsOpen the referer_spam_ajouter.php and/or referer_spam_supprimer.php files and search for SQL queries that use the 'url' GET parameter. Look for patterns like $url = $_GET['url'] followed by SQL LIKE clauses without prepared statements or sql_escape().Affected if The code directly uses $_GET['url'] or $url from GET requests inside SQL queries without parameterized binding or input sanitization functions.
-
Verify action accessibilityTest accessing the action handlers directly via URL patterns such as /?action=referer_spam_ajouter&url=test or /?action=referer_spam_supprimer&url=test using a web request tool. Check if the actions respond without requiring authentication.Affected if The actions return a valid SPIP response without redirecting to a login page or requiring authorization.
If the referer_spam plugin is installed with a version before 1.3.0 and contains the vulnerable action handlers with unprotected url parameter usage, the environment is affected by this SQL injection vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.3.0
Upgrade the referer_spam plugin to version 1.3.0 or later, which implements parameterized queries and input validation for the url parameter. If immediate patching is not possible, disable these action handlers or restrict access at the web server level.
1.3.0
- Update the referer_spam plugin to version 1.3.0 or later through the SPIP plugin administration interface
- Alternatively, download the updated plugin package from the SPIP extensions repository and replace the existing plugin files
- Verify the upgrade was successful by checking the plugin version in SPIP's plugin management panel
- Confirm that the referer_spam_ajouter and referer_spam_supprimer actions now properly handle the url parameter with input validation or parameterization
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27743 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-27743 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data