CVE-2013-5303 json
Unspecified vulnerability in the Store Locator (locator) extension before 3.1.5 for TYPO3 has unknown impact and remote attack vectors, rel…
published 13y ago modified 4mo ago also EUVD-2013-5143
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.9%
- EPSS 1.9% chance of exploitation in 30 days, percentile 79%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in the Store Locator (locator) extension before 3.1.5 for TYPO3 has unknown impact and remote attack vectors, related to "Insecure Unserialize."
Patch / fix
Is CVE-2013-5303 in your stack? 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.86% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
References
-
typo3.org
/teams/security/security-bulletins/typo3-extensions/typo3-ext-sa-2013-013
patch, vendor-advisory
-
typo3.org
/extensions/repository/view/locator
patch
-
secunia.com
/advisories/54350
third-party-advisory, vendor-advisory
-
osvdb.org
/95967
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/86233
vdb-entry
-
securityfocus.com
/bid/61606
vdb-entry
Sources
- CVE List CVE-2013-5303
- NVD CVE-2013-5303
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.