CVE-2026-27473
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 · uneditedSPIP before 4.4.9 allows Stored Cross-Site Scripting (XSS) via syndicated sites in the private area. The #URL_SYNDIC output is not properly sanitized on the private syndicated site page, allowing an attacker who can set a malicious syndication URL to inject persistent scripts that execute when other administrators view the syndicated site details.
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 confidenceSPIP before 4.4.9 contains a stored XSS vulnerability in the syndicated sites feature of the private area. The #URL_SYNDIC template output is not properly sanitized, allowing an attacker who can configure a syndicated site to inject malicious JavaScript that executes when other administrators view the syndicated site details page.
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>= 4.4.0, < 4.4.9CVSS 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
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.
-
Identify SPIP versionCheck the version.php file in the root directory or view the admin dashboard footer which displays the installed versionAffected if Version is 4.4.0 through 4.4.8 (inclusive)
-
Verify syndicated sites feature accessLog into the private area and navigate to Configuration > Syndication (or similar path depending on admin plugin) to confirm the syndicated sites feature is accessibleAffected if The syndicated sites configuration interface is available to your user account
-
Confirm user permissions for syndicated sitesCheck if your user role allows adding or editing syndicated sites in the syndication settings panelAffected if You have permission to add or modify syndicated site configurations
You are affected if your SPIP version is between 4.4.0 and 4.4.8 and you have access to configure syndicated sites in the private area.
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 · scoped4.4.9
Upgrade to SPIP version 4.4.9 or later which contains proper sanitization for the #URL_SYNDIC output.
SPIP 4.4.9 or later stable release
- Backup your SPIP installation and database before proceeding
- Download SPIP version 4.4.9 or later from the official SPIP repository (https://www.spip.net/en_download)
- Extract the new version files
- Replace the existing SPIP files with the new version, preserving your config/ and local/ directories if applicable
- Verify the upgrade was successful by logging into the private area
- Navigate to the syndicated sites section to confirm the XSS vulnerability in #URL_SYNDIC is now patched
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27473 — 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-27473 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