dbcve.org
SpipApplication

CVE-2007-4525

HIGH · 7.5 CVSS v2.0 Published 2007-08-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
PHP remote file inclusion vulnerability in inc-calcul.php3 in SPIP 1.7.2 allows remote attackers to execute arbitrary PHP code via a URL in the squelette_cache parameter, a different vector than CVE-2006-1702. NOTE: this issue has been disputed by third party researchers, stating that the squelette_cache variable is initialized before use, and is only used within the scope of a function

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 · moderate confidence

PHP remote file inclusion vulnerability in SPIP 1.7.2's inc-calcul.php3 allows arbitrary PHP code execution via the squelette_cache parameter. This is a different vector from CVE-2006-1702, though third-party researchers dispute the exploitability, claiming the variable is initialized before use and scoped within a function.

MitigationUpgrade SPIP to a patched version beyond 1.7.2, or apply vendor-supplied security patches to properly sanitize the squelette_cache parameter before use in file operations.

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
SpipApplication
Affected:= 1.7.2

CVSS 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
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify SPIP installation and version
    Check for SPIP by looking for its characteristic files (ecrire/inc-calcul.php3, ecrire/inc_version.php3) or check the page source of any SPIP page for a meta generator tag containing 'SPIP'. Review any version.php or inc_version.php3 file within the ecrire directory for the version number.
    Affected if The installed version is exactly 1.7.2 or if the version cannot be determined but the software appears to be SPIP from this era.
  2. Locate the vulnerable script
    Verify the presence of inc-calcul.php3 in the ecrire directory (typically ecrire/inc-calcul.php3). This file is required for the vulnerability to exist.
    Affected if The file ecrire/inc-calcul.php3 exists in the SPIP installation.
  3. Verify parameter handling in inc-calcul.php3
    Examine the source code of ecrire/inc-calcul.php3 and search for usage of the squelette_cache variable. Look for include(), require(), include_once(), or require_once() statements that use this variable without proper sanitization.
    Affected if The squelette_cache parameter is used in a file inclusion function without validation or sanitization being applied before the inclusion.
  4. Confirm web-accessible attack surface
    Determine if the ecrire directory or specifically inc-calcul.php3 is accessible via HTTP/HTTPS from the web server. Check web server configuration files (Apache .htaccess, nginx config) for restrictions on the ecrire directory.
    Affected if The vulnerable script is accessible over the network without authentication restrictions, allowing an attacker to supply the squelette_cache parameter via a URL.

You are affected if SPIP version 1.7.2 is running, the inc-calcul.php3 file exists, the squelette_cache parameter is used unsafed in file inclusion operations within that file, and the script is web-accessible to supply malicious parameter values.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade SPIP to a patched version beyond 1.7.2, or apply vendor-supplied security patches to properly sanitize the squelette_cache parameter before use in file operations.

Fix this in Spip Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-4525 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-4525 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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