# CVE-2013-4748: News system (news) extension for TYPO3 vulnerable to SQL Injection

> Remote attackers can execute arbitrary SQL commands in the TYPO3 News extension, potentially compromising database integrity and confidentiality.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Jul 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-rg6g-v4xm-g49q

## What is CVE-2013-4748?

CVE-2013-4748 is a high-severity SQL injection vulnerability in n/a, published on 1 Jul 2013. It can be exploited over the network, with no action from the victim.

### Official description

SQL injection vulnerability in the News system (news) extension before 1.3.3 for TYPO3 allows remote attackers to execute arbitrary SQL commands via unspecified vectors.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `georgringer/news` | Packagist | All versions | 1.3.3 |
| `georgringer/news` | Packagist | All versions | 1.3.3 |

Products: Georg Ringer News.

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

Upgrade georgringer/news to 1.3.3 or later.

## Is CVE-2013-4748 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-4748 is a high-severity SQL injection vulnerability in n/a, published on 1 Jul 2013. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-4748 in the wild and no public exploit code.

Affected packages and fixed versions:
- georgringer/news (Packagist): affected all versions; fixed in 1.3.3
- georgringer/news (Packagist): affected all versions; fixed in 1.3.3

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

## Sources

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

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