CVE-2013-7079 json
TYPO3 OpenID extension Open redirect vulnerability
published 12y ago modified 4mo ago also GHSA-838c-v5cq-hp33 , EUVD-2022-3092
- cvss
- 5.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist friendsoftypo3/openid 4.5.31, 4.7.16, 6.0.11, 6.1.6
Is CVE-2013-7079 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.21% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:P/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | friendsoftypo3/openid | >=4.5.0, <4.5.31 >=4.7.0, <4.7.16 >=6.0.0, <6.0.11 >=6.1.0, <6.1.6 |
4.5.31 4.7.16 6.0.11 6.1.6 |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
debian.org
/security/2014/dsa-2834
vendor-advisory, web
-
typo3.org
/teams/security/security-bulletins/typo3-core/typo3-core-sa-2013-004/
vendor-advisory
-
seclists.org
/oss-sec/2013/q4/473
mailing-list, web
-
securityfocus.com
/bid/64252
vdb-entry, web
-
nvd.nist.gov
/vuln/detail/CVE-2013-7079
advisory
-
github.com
/FriendsOfTYPO3/openid
package
-
typo3.org
/teams/security/security-bulletins/typo3-core/typo3-core-sa-2013-004
web
Sources
- CVE List CVE-2013-7079
- GitHub Advisory GHSA-838c-v5cq-hp33
- NVD CVE-2013-7079
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.