How severe is CVE-2013-7079?

No CVSS score has been assigned to CVE-2013-7079 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-7079?

CVE-2013-7079 affects the following packages: friendsoftypo3/openid (Packagist), friendsoftypo3/openid (Packagist), friendsoftypo3/openid (Packagist), friendsoftypo3/openid (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2013-7079?

Update friendsoftypo3/openid to 4.5.31 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-7079 is resolved across your whole dependency graph.

How do I detect CVE-2013-7079 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for friendsoftypo3/openid, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-7079 if there is no patch (or I can't update yet)?

Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Is CVE-2013-7079 actively exploited in the wild?

No public exploit code has been indexed for CVE-2013-7079 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2013-7079?

CVE-2013-7079 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 68th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2013-7079?

CVE-2013-7079 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2013-7079 published, and has it been updated?

CVE-2013-7079 was published on May 17, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2013-7079 — openid

CVE-2013-7079 is a Improper Input Validation vulnerability in friendsoftypo3/openid. A fix is available for friendsoftypo3/openid — see the affected versions and patch details below.

TYPO3 OpenID extension Open redirect vulnerability

Published

May 17, 2022

Updated

Nov 8, 2023

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Oct 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs68th percentile — riskier than 68% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

4 pkgs affected

🐘friendsoftypo3/openid🐘friendsoftypo3/openid🐘friendsoftypo3/openid🐘friendsoftypo3/openid

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Open redirect vulnerability in the OpenID extension in TYPO3 4.5.0 through 4.5.31, 4.7.0 through 4.7.16, 6.0.0 through 6.0.11, and 6.1.0 through 6.1.6 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via unspecified vectors.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`friendsoftypo3/openid`	≥ 4.5.0&&< 4.5.31	4.5.31`composer require friendsoftypo3/openid:^4.5.31`
🐘Packagist	`friendsoftypo3/openid`	≥ 4.7.0&&< 4.7.16	4.7.16`composer require friendsoftypo3/openid:^4.7.16`
🐘Packagist	`friendsoftypo3/openid`	≥ 6.0.0&&< 6.0.11	6.0.11`composer require friendsoftypo3/openid:^6.0.11`
🐘Packagist	`friendsoftypo3/openid`	≥ 6.1.0&&< 6.1.6	6.1.6`composer require friendsoftypo3/openid:^6.1.6`

Affected Products

1 product · 68 configurations

Application

typo3typo3

68 versions

4.5.04.5.14.5.24.5.34.5.44.5.54.5.64.5.74.5.84.5.94.5.104.5.11

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for friendsoftypo3/openid, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update friendsoftypo3/openid to 4.5.31 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-7079 is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-7079 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works