# CVE-2012-5558: Cross-site scripting in Smiley

> Authenticated users with admin permissions can inject arbitrary scripts via smiley acronyms in the Drupal Smiley module.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-x75f-hqp8-w29f

## What is CVE-2012-5558?

CVE-2012-5558 is a medium-severity cross-site scripting vulnerability in Smiley;Smileys Smiley, published on 9 Jan 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting (XSS) vulnerability in the Smiley module 6.x-1.x versions prior to 6.x-1.1 and Smileys module 6.x-1.x versions prior to 6.x-1.1 for Drupal allows remote authenticated users with the "administer smiley" permission to inject arbitrary web script or HTML via a smiley acronym.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2012-5558?

It affects 2 products.


Products: Smiley Project Smiley, Smileys Project Smileys.

## How do I fix CVE-2012-5558?

No fix has been published for CVE-2012-5558 yet. Limit exposure of the affected software until one is available.

## Is CVE-2012-5558 being exploited?

There is no known exploitation of CVE-2012-5558 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-5558 and fix it if it is affected.

What it is: CVE-2012-5558 is a medium-severity cross-site scripting vulnerability in Smiley;Smileys Smiley, published on 9 Jan 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2012-5558 in the wild and no public exploit code.

Affected product: Smiley;Smileys Smiley. 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-5558/ (Markdown: https://insights.sbomify.com/CVE-2012-5558/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-5558
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-5558
- OSV: https://osv.dev/vulnerability/CVE-2012-5558

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-5558/
Summaries are generated and may contain mistakes; the official description above is the record.