# CVE-2015-10133: Subscribe to Comments <= 2.1.2 - Local File Includion

> Administrative users can exploit a local file inclusion vulnerability to execute arbitrary PHP code and read sensitive data.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jul 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-rg2c-8v6w-j49r

## What is CVE-2015-10133?

CVE-2015-10133 is a high-severity path traversal vulnerability in markjaquith Subscribe to Comments, published on 19 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Subscribe to Comments for WordPress is vulnerable to Local File Inclusion in versions up to, and including, 2.1.2 via the Path to header value. This allows authenticated attackers, with administrative privileges and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included. This same function can also be used to execute arbitrary PHP code.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

## Which versions are affected by CVE-2015-10133?

It affects 1 product.


Products: Markjaquith Subscribe to Comments.

## How do I fix CVE-2015-10133?

No fix has been published for CVE-2015-10133 yet. Limit exposure of the affected software until one is available.

## Is CVE-2015-10133 being exploited?

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

Public exploit code:

- WordPress Subscribe Comments File Read Vulnerability (metasploit)

## Other vulnerabilities in markjaquith Subscribe to Comments

- [CVE-2024-8792](https://insights.sbomify.com/CVE-2024-8792/): Subscribe to Comments <= 2.3 - Reflected Cross-Site Scripting (medium 6.1)
- [CVE-2006-10001](https://insights.sbomify.com/CVE-2006-10001/): Subscribe to Comments Plugin subscribe-to-comments.php cross site scripting (low 3.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-10133 and fix it if it is affected.

What it is: CVE-2015-10133 is a high-severity path traversal vulnerability in markjaquith Subscribe to Comments, published on 19 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-10133 exists.

Affected product: markjaquith Subscribe to Comments. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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