CVE-2026-3576
A public proof of concept exists; no exploitation attested.
- Published2026-07-11
- WeaknessCWE-20
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
The Planyo Online Reservation System plugin for WordPress is vulnerable to Server-Side Request Forgery leading to Local File Inclusion in all versions up to, and including, 3.0. The ulap.php file acts as an AJAX proxy and is directly accessible without WordPress bootstrapping or any authentication. The send_http_post() function validates the host of the provided URL against an allowlist that includes 'localhost', but critically fails to validate the URL scheme/protocol. This makes it possible for unauthenticated attackers to supply a file:// URL (e.g., file://localhost/etc/passwd) which bypasses the host allowlist check because parse_url() returns 'localhost' as the host. The URL is then passed to curl_init() or fopen(), both of which support the file:// protocol, allowing the attacker to read arbitrary local files on the server and have their contents returned in the HTTP response. This can lead to disclosure of sensitive files such as /etc/passwd, wp-config.php (containing database credentials and authentication keys), and other server-side files.
Timeline
dates in UTC- 2026-07-1105:16CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-3576?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-3576?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
Neither OSV.dev nor the vendor advisories we read list affected versions for CVE-2026-3576 yet.
Fix
No fix published by the sources we read yet. NVD record
Detection
read 2026-10-23 19:25 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
Sources
- NVDCVE recordread 2026-10-23
- CISA-ADPSSVC decisionnone2026-07-13
- OpenCVESSVC decisionnone—
- CNACVSS 3.17.2read 2026-10-23
- CNAweakness (CWE)CWE-20read 2026-10-23
- FIRST EPSSEPSS score8.8 %2026-10-22
- PoC-in-GitHubproof of concept1read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
- Published
- 2026-07-11
- Last Modified
- 2026-07-13
- NVD status
- Deferred
Frequently asked questions
What is CVE-2026-3576?
Is CVE-2026-3576 actively exploited?
What is the CVSS score for CVE-2026-3576?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.