Security readout for executives and security teams
Plain-English summary
This affects the WordPress Subscribe to Comments plugin up to version 2.1.2. A WordPress administrator could abuse a local file inclusion flaw to make the server load arbitrary files, potentially exposing sensitive data or executing PHP code. The source bundle does not show active exploitation.
Executive priority
Treat as high priority for any WordPress estate using this legacy plugin, especially where administrator accounts are shared, weakly protected, or externally managed. It is less urgent for sites without the plugin or where no vulnerable version is present.
Technical view
The flaw is CWE-98 local file inclusion through the Path to header value. CVSS 3.1 is 7.2 high, with network attack vector, low complexity, no user interaction, and high privileges required. Impact is high for confidentiality, integrity, and availability when an administrator-level attacker can include executable PHP content.
Likely exposure
Exposure is limited to WordPress installations running Subscribe to Comments versions up to and including 2.1.2. Practical risk depends on whether untrusted or compromised administrator accounts exist. The structured affected data appears inconsistent, so version validation should rely on plugin inventory and vendor advisories.
Exploitation context
The bundle cites public advisories and disclosure listings from dxw, Full Disclosure, Packet Storm, Wordfence, and WordPress Trac. It does not include CISA KEV status or another cited source proving active exploitation. The vulnerability requires authenticated administrator privileges, reducing broad internet-scale exposure but increasing risk after admin compromise.
Researcher notes
Analysis is source-limited. The key technical claim is local file inclusion via the Path to header value in Subscribe to Comments <= 2.1.2. CVSS indicates PR:H, so validation should focus on installed plugin versions, administrator account exposure, and vendor-confirmed remediation state.
Mitigation direction
- Inventory WordPress sites for Subscribe to Comments and installed version.
- Upgrade to a vendor-supported fixed release, or remove/disable if no maintained release is available.
- Restrict WordPress administrator accounts and review who has admin privileges.
- Monitor vendor, Wordfence, and WordPress plugin guidance for confirmed fixed versions.
- Review uploaded files and web logs if vulnerable versions were exposed.
Validation and detection
- Confirm whether Subscribe to Comments is installed and whether version is <= 2.1.2.
- Verify only trusted users have administrator privileges on affected WordPress instances.
- Check whether remediation removed the vulnerable plugin path or upgraded it.
- Review logs for unexpected file inclusion behavior or suspicious administrator activity.
- Document any uncertainty where plugin version or patch status cannot be confirmed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-98: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2015-10133 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/f92784a7-f2b3-47f8-b03f-4e234b57e40a?source=cveCVE reference
- https://advisories.dxw.com/advisories/admin-only-local-file-inclusion-and-arbitrary-code-execution-in-subscribe-to-comments-2-1-2/CVE reference
- https://seclists.org/fulldisclosure/2015/Jul/71CVE reference
- https://packetstormsecurity.com/files/132694/CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=1198281%40subscribe-to-comments&new=1198281%40subscribe-to-comments&sfp_email=&sfph_mail=CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.