CVE-2025-71242
Unauthorized Content Disclosure in SPIP AJAX Fragments Before
Publication date: 2026-02-19
Last updated on: 2026-03-02
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| spip | spip | From 4.1.0 (inc) to 4.1.20 (exc) |
| spip | spip | From 4.2.0 (inc) to 4.2.17 (exc) |
| spip | spip | From 4.3.0 (inc) to 4.3.6 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-285 | The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability affects SPIP versions before 4.3.6, 4.2.17, and 4.1.20. It allows unauthorized content disclosure in the private area of the application. Specifically, the application does not properly check authorization when displaying content of articles and sections (rubriques) in AJAX-loaded fragments. As a result, an authenticated attacker can access restricted content that they should not be able to see.
Additionally, this vulnerability is not mitigated by the SPIP security screen, meaning the usual security protections do not prevent this unauthorized access.
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized disclosure of restricted or private content within the SPIP application. An attacker with authenticated access can view sensitive articles and sections that should be protected, potentially exposing confidential information.
The impact is limited to confidentiality, as the vulnerability does not affect integrity or availability of the system.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know