highCVE-2026-3576

Planyo online reservation system <= 3.0 - Unauthenticated Server-Side Request Forgery via 'ulap_url' Parameter

Q: What is affected by CVE-2026-3576?

Planyo online reservation system versions listed as affected should be reviewed: *-3.0.

Q: What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

Q: How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

Q: How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.

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.

ProductPlanyo online reservation system

CVSS7.2

EPSS0.00357

UpdatedJuly 13, 2026

Quick answer

Planyo online reservation system should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

*-3.0

Fixed versions

How to fix it

Planyo online reservation system is affected by CVE-2026-3576, a server-side request forgery issue in versions up to 3.0. Wordfence lists the official remediation as updating to version 3.1, or a newer patched version. Prioritize internet-facing WordPress sites, sites with public registration, customer portals, Elementor/page-builder surfaces, reservation or booking workflows, and admin workflows where the vulnerable feature is enabled. If immediate patching is not possible, disable the affected plugin or feature, restrict access, and monitor for exploitation until the update is installed.

Inventory every WordPress site that has Planyo online reservation system installed, including production, staging, multisite, client, WooCommerce, marketplace, and booking environments.
Confirm the installed Planyo online reservation system version and compare it with the affected range from the Wordfence advisory.
Update Planyo online reservation system to version 3.1, or to a newer vendor-supported patched version from the official WordPress update channel.
If the update cannot be applied immediately, disable Planyo online reservation system or the affected feature and restrict access with roles, authentication, WAF rules, or temporary route blocking.
Review outbound HTTP logs, webhook activity, metadata endpoint access, internal service requests, and unusual callbacks triggered by the WordPress site.
Rotate administrator sessions, API keys, webhook secrets, payment or integration tokens, and affected credentials if logs or content review suggest compromise.
Clear WordPress, object, CDN, page-builder, security plugin, WooCommerce, and browser caches after patching so vulnerable assets or stored payloads are not served.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

Confirm the running Planyo online reservation system version is version 3.1 or newer, and record the patched version in the remediation ticket.
Verify attackers cannot make the site request arbitrary internal, metadata, loopback, or private-network URLs through the affected feature.
Review web server, WordPress, security plugin, WAF, database, WooCommerce, and application logs for exploitation attempts before and after the fix.
Retest normal visitor, subscriber, customer, vendor, editor, administrator, checkout, form, API, booking, reservation, invoice, or integration workflows to confirm expected behavior still works.
Run a fresh Fixnx scan and document the public exposure state, patched version, log review, and any cleanup evidence.

Related categories

WordPress PHP Path Traversal SSRF

Trusted references

Wordfence advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Wordfence advisoryWordfence, NVD

FAQ

What is affected by CVE-2026-3576?

Planyo online reservation system versions listed as affected should be reviewed: *-3.0.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.