# CVE-2013-7472: Cross-site scripting in n/a

> Cross-site scripting vulnerability in the Count per Day WordPress plugin allows attackers to inject malicious scripts via the daytoshow parameter.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Jun 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fccf-x2r5-c5h7

## What is CVE-2013-7472?

CVE-2013-7472 is a medium-severity cross-site scripting vulnerability in n/a, published on 15 Jun 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The "Count per Day" plugin before 3.2.6 for WordPress allows XSS via the wp-admin/?page=cpd_metaboxes daytoshow parameter.

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

## Which versions are affected by CVE-2013-7472?

It affects 1 product.


Products: Count per Day Project Count per Day.

## How do I fix CVE-2013-7472?

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

## Is CVE-2013-7472 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-5533](https://insights.sbomify.com/CVE-2015-5533/): SQL injection in n/a (high 7.2)
- [CVE-2012-6714](https://insights.sbomify.com/CVE-2012-6714/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2012-0896](https://insights.sbomify.com/CVE-2012-0896/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-7472 and fix it if it is affected.

What it is: CVE-2013-7472 is a medium-severity cross-site scripting vulnerability in n/a, published on 15 Jun 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-7472 in the wild and no public exploit code.

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-2013-7472/ (Markdown: https://insights.sbomify.com/CVE-2013-7472/index.md)
```

## Sources

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

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