# CVE-2013-5100: Static Methods since 2007 (div2007) extension for TYPO3 vulnerable to Cross-site Scripting

> Remote attackers can inject arbitrary web script or HTML via the div2007 extension, potentially compromising user sessions or data.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 9 Aug 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4mm3-xgc2-656r

## What is CVE-2013-5100?

CVE-2013-5100 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Aug 2013. 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

Cross-site scripting (XSS) vulnerability in the Static Methods since 2007 (div2007) extension before 0.10.2 for TYPO3 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors, related to the t3lib_div::quoteJSvalue function.

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

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

2 open source packages ship an affected version, including jambagecom/div2007. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `jambagecom/div2007` | Packagist | All versions | 0.10.2 |
| `jambagecom/div2007` | Packagist | All versions | 0.10.2 |

Products: Franz Holzinger Static Methods.

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

Upgrade jambagecom/div2007 to 0.10.2 or later.

## Is CVE-2013-5100 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-5100 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Aug 2013. 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-5100 in the wild and no public exploit code.

Affected packages and fixed versions:
- jambagecom/div2007 (Packagist): affected all versions; fixed in 0.10.2
- jambagecom/div2007 (Packagist): affected all versions; fixed in 0.10.2

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

## Sources

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

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