CVE-2013-4295 json
Apache Shindig PHP Sensitive Information Disclosure
published 13y ago modified 4mo ago also GHSA-6jvw-rpw4-gj4x , EUVD-2022-2816
- cvss
- 5.3
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 11.7%
- EPSS 11.7% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB
Summary
The gadget renderer in Apache Shindig 2.5.0 for PHP allows remote attackers to obtain sensitive information via an XML document containing an external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue.
Patch / fix
Is CVE-2013-4295 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 FencerTimeline
- First public exploit (EDB-38813)
- Published
Exploit prediction
11.69% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-38813 Apache Shindig - XML External Entity Information Disclosure remote, 2013-10-21
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.shindig:shindig-php | >=2.5.0-beta1, <2.5.0-update1 |
2.5.0-update1 |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
shindig.apache.org
/security.html
web, patch, vendor-advisory
-
securityfocus.com
/bid/63260
vdb-entry, web
-
archives.neohapsis.com
/archives/bugtraq/2013-10/0104.html
mailing-list, web
-
nvd.nist.gov
/vuln/detail/CVE-2013-4295
advisory
-
github.com
/apache/shindig
package
Sources
- CVE List CVE-2013-4295
- GitHub Advisory GHSA-6jvw-rpw4-gj4x
- NVD CVE-2013-4295
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.