CVE-2012-4331 Other in n/a
Critical 10.0
Published
Updated
Check this codebase for CVE-2012-4331 and fix it if it is affected.
What it is: CVE-2012-4331 is a critical vulnerability in Spip Spip, published on 14 Aug 2012.
Exploitation: There is no known exploitation of CVE-2012-4331 in the wild and no public exploit code.
Affected product: Spip Spip. 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-2012-4331/ (Markdown: https://insights.sbomify.com/CVE-2012-4331/index.md)
Multiple unspecified vulnerabilities in SPIP CMS allow attackers to potentially compromise the system, requiring an upgrade to a patched version.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- Available
What is CVE-2012-4331?
CVE-2012-4331 is a critical vulnerability in Spip Spip, published on 14 Aug 2012.
Official description
Multiple unspecified vulnerabilities in SPIP before 1.9.2.o, 2.0.x before 2.0.18, and 2.1.x before 2.1.13 have unknown impact and attack vectors that are not related to cross-site scripting (XSS), different vulnerabilities than CVE-2012-2151.
Which versions are affected by CVE-2012-4331?
It affects 1 product.
Products include Spip Spip.
How do I fix CVE-2012-4331?
Upgrade to a fixed version.
Is CVE-2012-4331 being exploited?
There is no known exploitation of CVE-2012-4331 in the wild and no public exploit code.
Other vulnerabilities in Spip Spip
Sources
Also known as DEBIAN-CVE-2012-4331, GHSA-2phr-4qpj-wc46.