Skip to content

CVE-2026-3576

Improper Input Validation: Is CVE-2026-3576 real, exploitable, or a false positive? Here's the community verdict.

signals

public sources

Exploited in wild
Not listed
CISA KEV
Public exploit
Exploit-DB +1
Metasploit/EDB/PoC
Base severity
7.2 High
CVSS
Exploitation prob.
13%
FIRST EPSS
Weakness
CWE-20 · Improper Input Validation
CWE

Moderate signals. Triage by your actual exposure and reachability.

public exploits

links to sources — we don’t host code

A working exploit is publicly available from a maintained source. Treat this as higher urgency and verify your exposure.

baseline read

auto · not a community verdict

Low signal — verdict needed

Few public signals point to active risk. Whether a scanner hit here is a true or false positive depends on your version and config — community verdicts decide.

Based on CVSS · FIRST EPSS

Confirm or dispute →

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

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.

Published

Embed this verdict
TruePositive verdict for CVE-2026-3576
Markdown
[![TruePositive verdict](https://www.truepositive.app/cve/CVE-2026-3576/badge.svg)](https://www.truepositive.app/cve/CVE-2026-3576)
HTML
<a href="https://www.truepositive.app/cve/CVE-2026-3576"><img src="https://www.truepositive.app/cve/CVE-2026-3576/badge.svg" alt="TruePositive verdict for CVE-2026-3576"></a>

Live badge that updates automatically as the community verdict changes.

Community ground truth

Be the first practitioner to weigh in

So far this is only TruePositive's editorial baseline from public sources. Add your real-world verdict below — it becomes the signal the next person triaging this relies on.

🥇 The first 50 practitioners to contribute earn a Founding Contributor badge.

In your experience, is this finding real and exploitable?

awaiting field verdicts
Real, but not a risk here
Not a real issue

Curated baseline: TruePositive's read from public sources is Real & exploitable — a starting point, not a community verdict.

No account needed. Anonymous verdicts post as an unverified signal. Log in to make yours verified and earn reputation.

Field notes & remediation

Verdicts are the quick signal. Notes are the evidence and fixes behind them.

  • 0
    Field note · TruePositive EditorialCurated

    A working public exploit is published for this, so the barrier to attack is low. FIRST EPSS estimates about a 13% chance of exploitation in the next 30 days, which is high relative to most CVEs. It is reachable over the network with no authentication and no user interaction, which is the most dangerous profile. Patch this on priority and confirm the fix holds.

Add a field note or remediationoptional
Note type

What are you adding?

Markdown supported · minimum 20 characters.

Same weakness: CWE-20 · Improper Input Validation.