# CVE-2026-3576: Planyo online reservation system <= 3.0 - Unauthenticated Server-Side Request Forgery via 'ulap_url' Parameter

> Unauthenticated attackers can exploit SSRF to read arbitrary local files, including sensitive configuration files, via the ulap_url parameter.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2026
- **Updated:** 13 Jul 2026
- **Also known as:** GHSA-jjq9-3x6f-75pj

## What is CVE-2026-3576?

CVE-2026-3576 is a high-severity server-side request forgery vulnerability in xtreeme Planyo online reservation system, published on 11 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-3576?


## How do I fix CVE-2026-3576?

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

## Is CVE-2026-3576 being exploited?

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

Public exploit code:

- Wordpress Plugin Planyo Online Reservation System <= 3.0 - Arbitrary File Read via SSRF (github_poc): https://github.com/anirbala98/CVE-2026-3576
- Wordpress Planyo Online Reservation System Arbitrary File Read (CVE-2026-3576) (metasploit)
- Planyo_Online_Reservation_System  3.0 - Arbitrary File Read via SSRF (exploitdb)
- Planyo Online Reservation System <= 3.0 - Arbitrary File Read (nuclei): http/cves/2026/CVE-2026-3576.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-3576 and fix it if it is affected.

What it is: CVE-2026-3576 is a high-severity server-side request forgery vulnerability in xtreeme Planyo online reservation system, published on 11 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-3576 exists.

Affected product: xtreeme Planyo online reservation system. 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-2026-3576/ (Markdown: https://insights.sbomify.com/CVE-2026-3576/index.md)
```

## Sources

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

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