Skip to main content

SimplePie EUVDEUVD-2026-102346

| CVE-2026-111234 HIGH
External Control of File Name or Path (CWE-73)
2026-10-15 VulnCheck
8.2
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Induce app to fetch attacker feed
  2. Exploit
    Return file:// redirect or autodiscovery link
  3. Execution
    file_get_contents() reads local file
  4. Impact
    Exfiltrate server file contents

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V5 - File Handling File name/path control
Exploitation Conditions

Requires the victim application to use SimplePie (through 1.9.0) to fetch a feed whose server responses or URL the attacker can influence, and relies on local-file fetching being effective - the pre-patch default, since set_allow_local_files() and the http(s) redirect/autodiscovery restrictions did not yet exist. The attacker then returns an HTTP Location redirect header or an autodiscovery <link> pointing to a file:// path, causing file_get_contents() to read a local file. Limiting factors: the attacker must control the feed server's responses or inject a malicious feed URL into the target application (not a default endpoint), which is reflected in the CVSS AC:H and AT:P metrics; disclosure is bounded to files readable by the web-server process; and patched versions refuse non-http(s) redirects and disable local-file fetching by default.

Impact

The supplied CVSS 4.0 vector rates this 8.2 (High), driven by network reachability (AV:N), no required privileges (PR:N), no user interaction (UI:N) and high confidentiality impact (VC:H), with integrity and availability unaffected (VI:N/VA:N). Crucially the same vector carries AC:H and AT:P, signalling that reliable exploitation depends on specific preconditions rather than trivial drive-by access. Publicly available exploit code exists (the abraxas/pfsense-rss-file-redirect PoC referenced in the data), but there is no CISA KEV listing and no EPSS score was provided, so there is no evidence of widespread active exploitation - this should be treated as a credible, proof-backed vulnerability rather than a mass-exploited emergency. My own CVSS 3.1 assessment lands lower (~5.9) than the headline 8.2 because the attacker must control or inject a feed source and rely on redirect/autodiscovery abuse, consistent with the high-complexity rating. No SSVC decision data was supplied. Overall this is a genuine priority specifically for PHP applications that fetch attacker-influenced feeds, but the AC:H/AT:P conditions temper the raw score.

Exploit ScenarioDerived

A malicious or attacker-influenced feed server responds to a SimplePie fetch with a Location redirect header or an autodiscovery link pointing to a file:// path (e.g. file:///etc/passwd or an application config file). SimplePie follows it and file_get_contents() reads the local file, surfacing its contents through the parsed feed where the attacker can harvest them. A public proof-of-concept (abraxas/pfsense-rss-file-redirect) demonstrates the redirect-based variant, and the CVSS AC:H complexity means the attacker must set up the malicious feed response rather than exploit a default endpoint.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
1 public PoC Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 15, 2026

Local file disclosure in SimplePie through 1.9.0 lets a malicious or compromised feed server read files on the host running the PHP application: by replying to a feed request with an HTTP Location redirect - or by planting an autodiscovery <link> - that points at a file:// path, the library follows the reference and reads the target file into the parsed feed. Exploitation requires no privileges (PR:N) but does require the attacker to control the feed server's responses or inject a feed URL into the application (AC:H, AT:P), and disclosure is bounded to files readable by the web-server process. Vendor fix is available via upstream PR 991, public exploit code exists (a PoC targeting pfSense's RSS widget has been published), and no confirmed active exploitation (CISA KEV) was identified at time of analysis.

RemediationAI

Update SimplePie past 1.9.0 to a release containing the fix from upstream PR 991 (https://github.com/simplepie/simplepie/pull/991, tracked at https://github.com/simplepie/simplepie/issues/968); the vendor reports a patch as available, and the change both refuses non-http(s) redirect/autodiscovery targets via Misc::is_remote_uri() and defaults local-file fetching to off unless an operator explicitly calls set_allow_local_files(true). Note that the merged fix is a PR/commit - if no tagged patched release is yet published in your dependency channel, apply the commit or vendor-pin the patched code, and confirm the released version number before relying on a package upgrade. If an immediate upgrade is impossible, apply the same policy yourself: wrap or replace the HTTP client so non-http(s) URLs and redirect Location values are rejected (the patch adds exactly this via UrlPolicy/NotAllowedException in Psr18Client), and disable or remove any SimplePie consumer that fetches feeds supplied by untrusted sources - the trade-off is that legitimate local-file or relative-path feed sources will stop working, which is the intended security posture. Additional compensating controls for the pre-patch default: restrict outbound feed fetching to a known allow-list of feed hosts to shrink the attacker-controlled-server surface; run the PHP web-server process with the least privilege possible and constrain it with PHP open_basedir (side effect: may break unrelated file access in the same pool and is not a complete boundary); and treat the feed-fetching endpoint as a trust boundary, since redirects to file:// are only dangerous when the attacker can steer the feed URL or its server responses. See the VulnCheck advisory (https://www.vulncheck.com/advisories/simplepie-through-1.9.0-local-file-read-via-file-redirect) for confirmed affected ranges and the demonstration exploit at https://github.com/abraxas/pfsense-rss-file-redirect.

Affected VersionsENISA

simplepie 0 ≤1.9.0

Affected Packages

euvd simplepie no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

SimplePie is a widely embedded PHP library for parsing RSS/Atom feeds; it fetches and dereferences remote feed URLs, follows redirects, and processes autodiscovery links from HTML pages. The root cause is CWE-73 (External Control of File Name or Path): the library accepted arbitrary URI schemes for feed locations and redirect targets, so a Location header or an autodiscovery candidate could resolve to a file:// URI and be passed to file_get_contents(), which happily reads local filesystem paths. The vulnerable flow lives in src/File.php (redirect handling around lines 145-220 of the pre-patch file) and in the HTTP client layer (src/HTTP/Psr18Client.php lines 75-157 and src/HTTP/FileClient.php), where no scheme allow-list existed prior to the fix. The upstream patch introduces Misc::is_remote_uri() gating that refuses any non-http(s) redirect or final requested URI, adds a NotAllowedException and a UrlPolicy hook to Psr18Client, and disables local-file fetching by default behind the new SimplePie::set_allow_local_files() opt-in - i.e., a defense-in-depth fix that closes both the initial-URL path and the post-redirect path. The assessed CVSS 3.1 vector is AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N, matching a remote-triggered confidentiality-only flaw that depends on attacker influence over feed content and on the pre-patch default of permitting local-file fetches.

Know when Simplepie gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 8.2 HIGH
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
vuln.today AI 5.9 MEDIUM

Network-reachable but AC:H because the attacker must control feed responses and abuse redirect/autodiscovery; PR:N/UI:N as no target auth is needed; C:H only, I/A unaffected.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
High
Attack Requirements
Present
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

SimplePie through 1.9.0 contains a local file read vulnerability that allows malicious feed servers to read server files by supplying file:// URLs in redirects or autodiscovery links. Attackers can return a Location header or feed link pointing to a file:// path, causing file_get_contents() to read files accessible to the web server process.

Technical POC Analysis

CWE-73, External Control of File Name or Path.

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Latest POC

1 public PoC link from github

Sign in to open the public PoC links collected for this CVE.

Executive ViewAI

Why It Matters

SimplePie versions through 1.9.0 contain a high-severity local file disclosure vulnerability that allows an unauthenticated attacker to read files on the host running the PHP application by manipulating feed server responses. Organizations using SimplePie, including those leveraging pfSense's RSS widget, are at risk of exposure of sensitive files such as configuration data or credentials. Publicly available exploit code exists, though no confirmed active exploitation (CISA KEV) has been observed; Patch available per vendor advisory.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 78% exploitable
Prevalence
High
widely-used PHP feed parser, bundled by WordPress and many CMS apps
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

61
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +41
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy