# CVE-2012-4547: Cross-site scripting in n/a

> Unspecified vulnerability in AWStats awredir.pl script, classified as Cross-Site Scripting, allowing potential malicious script injection.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 31 Oct 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-4547, GHSA-vx3h-mw4x-r37x

## What is CVE-2012-4547?

CVE-2012-4547 is a medium-severity cross-site scripting vulnerability in n/a, published on 31 Oct 2012. It can be exploited over the network.

### Official description

Unspecified vulnerability in awredir.pl in AWStats before 7.1 has unknown impact and attack vectors.

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

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

It affects 1 product.


Products: Laurent Destailleur Awstats.

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

Upgrade to a fixed version.

## Is CVE-2012-4547 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-4547 exists.

Public exploit code:

- AWStats 6.95/7.0 - 'awredir.pl' Cross-Site Scripting (nuclei): http/cves/2012/CVE-2012-4547.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2012-4547 is a medium-severity cross-site scripting vulnerability in n/a, published on 31 Oct 2012. It can be exploited over the network.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-4547 exists.

Affected product: n/a. 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-4547/ (Markdown: https://insights.sbomify.com/CVE-2012-4547/index.md)
```

## Sources

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

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