How severe is CVE-2012-1188?

No CVSS score has been assigned to CVE-2012-1188 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2012-1188?

CVE-2012-1188 affects the following packages: forkcms/forkcms (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2012-1188?

Update forkcms/forkcms to 3.2.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-1188 is resolved across your whole dependency graph.

How do I detect CVE-2012-1188 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for forkcms/forkcms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2012-1188 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2012-1188 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2012-1188, including 2 documented proof-of-concept exploits on Exploit-DB and 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2012-1188?

CVE-2012-1188 has an EPSS (Exploit Prediction Scoring System) score of 4.5%, placing it in the 91th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2012-1188?

CVE-2012-1188 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2012-1188 published, and has it been updated?

CVE-2012-1188 was published on May 17, 2022 and was last updated on January 12, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2012-1188 — forkcms

Fix: forkcms/forkcms@1269fe8

CVE-2012-1188 is a Cross-site Scripting (XSS) vulnerability in forkcms/forkcms. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for forkcms/forkcms — see the affected versions and patch details below.

Fork CMS Multiple XSS Vulnerabilities

Published

May 17, 2022

Updated

Jan 12, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

3 known

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

4.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐘forkcms/forkcms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Multiple cross-site scripting (XSS) vulnerabilities in Fork CMS before 3.2.7 allow remote attackers to inject arbitrary web script or HTML via the (1) type or (2) querystring parameters to private/en/error or (3) name parameter to private/en/locale/index.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`forkcms/forkcms`	all versions	3.2.7`composer require forkcms/forkcms:^3.2.7`

Affected Products

1 product · 1 configurations

Application

fork cmsfork-cms

≤ 3.2.6

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-36893webappsphp✓ Verified

Fork CMS 3.x - '/private/en/locale/index?name' Cross-Site Scripting

by anonymous · Feb 28, 2012

Exploit-DB Source

EDB-36894webappsphp✓ Verified

Fork CMS 3.x - '/backend/modules/error/actions/index.php?parse()' Multiple Error Display Cross-Site Scripting Vulnerabilities

by anonymous · Feb 28, 2012

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for forkcms/forkcms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update forkcms/forkcms to 3.2.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-1188 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

Multiple cross-site scripting (XSS) vulnerabilities in Fork CMS before 3.2.7 allow remote attackers to inject arbitrary web script or HTML via the (1) type or (2) querystring parameters to `private/en/error` or (3) name parameter to `private/en/locale/index`.

O3 Security · Impact-Aware SCA

Is CVE-2012-1188 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works