# CVE-2013-4295: Apache Shindig PHP Sensitive Information Disclosure

> Remote attackers can obtain sensitive information via XML External Entity injection in the Apache Shindig PHP gadget renderer.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Oct 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6jvw-rpw4-gj4x

## What is CVE-2013-4295?

CVE-2013-4295 is a medium-severity vulnerability in n/a, published on 24 Oct 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

2 open source packages ship an affected version, including org.apache.shindig:shindig-php. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.shindig:shindig-php` | Maven | From 2.5.0-beta1 | 2.5.0-update1 |
| `org.apache.shindig:shindig-php` | Maven | From 2.5.0-beta1 | 2.5.0-update1 |

Products: Apache Shindig.

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

Upgrade org.apache.shindig:shindig-php to 2.5.0-update1 or later.

## Is CVE-2013-4295 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-4295 exists.

Public exploit code:

- Apache Shindig - XML External Entity Information Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2026-66256](https://insights.sbomify.com/CVE-2026-66256/): Deserialization in Apache Shindig Common (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-4295 is a medium-severity vulnerability in n/a, published on 24 Oct 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-4295 exists.

Affected packages and fixed versions:
- org.apache.shindig:shindig-php (Maven): affected from 2.5.0-beta1; fixed in 2.5.0-update1
- org.apache.shindig:shindig-php (Maven): affected from 2.5.0-beta1; fixed in 2.5.0-update1

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

## Sources

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

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