Skip to content
Fencer Intel
medium 4.3

CVE-2012-2331 json

Cross-site scripting (XSS) vulnerability in serendipity/serendipity_admin_image_selector.php in Serendipity before 1.6.1 allows remote atta…

published 2012-08-13 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-2324

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.7%
EPSS 4.7% chance of exploitation in 30 days, percentile 91%
public exploits
1
Exploit-DB

Summary

Cross-site scripting (XSS) vulnerability in serendipity/serendipity_admin_image_selector.php in Serendipity before 1.6.1 allows remote attackers to inject arbitrary web script or HTML via the serendipity[textarea] parameter. NOTE: this issue might be resultant from cross-site request forgery (CSRF).

Patch / fix

Timeline

  1. First public exploit (EDB-18884)
  2. Published

Exploit prediction

4.68% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-18884 S9Y Serendipity 1.6 - 'Backend' Cross-Site Scripting / SQL Injection webapps, 2012-05-08
  • github.com https://github.com/s9y/Serendipity/commit/264bf55719baacc069ff9d3cc35f0c349cde11e3 referenced PoC, tagged "exploit" by a source, unverified
  • rul3z.de http://www.rul3z.de/index.php?/214-KORAMISADV2012-001-Serendipity-1.6-Backend-Cross-Site-Scripting-and-SQL-Injection-vulnerability.html referenced PoC, tagged "exploit" by a source, unverified
  • securityfocus.com http://www.securityfocus.com/bid/53418 referenced PoC, tagged "exploit" by a source, unverified
  • koramis.com http://www.koramis.com/advisories/2012/KORAMIS-ADV2012-001.txt referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.