CVE-2026-3576

HIGHPre-NVD 7.27.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-07-11. A secondary CVSS source baseline 7.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Weaponized
7.2EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit code is available (Metasploit, other public proof-of-concept code)
CISA-KEV: Not listedEPSS PROB: 8.8%CVSS: 7.2Exploit: Metasploit · other public PoCExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (Wordfence) lists xtreeme Planyo online reservation system versions up to and including 3.0 as affected. No release containing a fix is confirmed on record.

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.

CVSS v3
7.2
EG Score
7.2HIGHmedium confidence
EG Risk
73
EG Risk 73/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity72% × 45%
The EG Score, 7.2 of 10.
Exploitation65% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 2 (Weaponized): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
8.8%
EPSS %ILE
95th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 11, 2026

Last Modified

July 13, 2026

References (12)

Vendor Advisories for CVE-2026-3576(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 36× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 223 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 124 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 8.8% · 95th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 8.8% · 95th percentile
  3. 2026-10-12 16:11 UTCEG score recompute
  4. 2026-10-11 19:53 UTCEG score recompute
  5. 2026-10-11 17:06 UTCEG score recompute
  6. 2026-10-11 14:33 UTCEG score recompute
  7. 2026-10-11 13:48 UTCEPSS rescoreEPSS 8.8% · 95th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 8.8% · 95th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 8.8% · 95th percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 8.8% · 95th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 8.8% · 95th percentile
  12. 2026-10-06 15:17 UTCEPSS rescoreEPSS 8.8% · 95th percentile
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 8.8% · 95th percentile
  14. 2026-10-03 14:25 UTCEPSS rescoreEPSS 8.8% · 95th percentile
  15. 2026-10-01 19:50 UTCEPSS rescoreEPSS 8.8% · 95th percentile
  16. 2026-10-01 14:54 UTCEG score recompute
  17. 2026-10-01 14:54 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  18. 2026-09-30 15:03 UTCEPSS rescoreEPSS 8.8% · 95th percentile
  19. 2026-09-28 13:51 UTCEPSS rescoreEPSS 8.8% · 95th percentile
  20. 2026-09-28 09:43 UTCEG score recompute
  21. 2026-09-28 09:43 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  22. 2026-09-27 13:48 UTCEPSS rescoreEPSS 8.8% · 95th percentile
  23. 2026-09-26 15:58 UTCEPSS rescoreEPSS 8.8% · 95th percentile
  24. 2026-09-26 00:26 UTCEPSS rescoreEPSS 8.8% · 95th percentile
  25. 2026-09-24 10:29 UTCEG score recompute
Show 74 more
  1. 2026-09-24 10:29 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  2. 2026-09-23 05:41 UTCEG score recompute
  3. 2026-09-23 05:41 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  4. 2026-09-20 20:15 UTCEPSS rescoreEPSS 13% · 96th percentile
  5. 2026-09-18 19:28 UTCEPSS rescoreEPSS 13% · 96th percentile
  6. 2026-09-18 05:12 UTCEG score recompute
  7. 2026-09-18 05:12 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  8. 2026-09-17 19:30 UTCEPSS rescoreEPSS 13% · 96th percentile
  9. 2026-09-16 14:08 UTCEPSS rescoreEPSS 13% · 96th percentile
  10. 2026-09-16 05:15 UTCEPSS rescoreEPSS 13% · 96th percentile
  11. 2026-09-15 03:11 UTCEPSS rescoreEPSS 13% · 96th percentile
  12. 2026-09-14 11:42 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  13. 2026-09-13 23:37 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  14. 2026-09-13 08:08 UTCEG score recompute
  15. 2026-09-13 08:08 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  16. 2026-09-12 15:01 UTCEPSS rescoreEPSS 13% · 96th percentile
  17. 2026-09-12 14:27 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  18. 2026-09-12 02:21 UTCEG score recompute
  19. 2026-09-12 02:21 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  20. 2026-09-11 14:53 UTCEPSS rescoreEPSS 13% · 96th percentile
  21. 2026-09-11 09:37 UTCEPSS rescoreEPSS 13% · 96th percentile
  22. 2026-09-10 09:34 UTCEPSS rescoreEPSS 13% · 96th percentile
  23. 2026-09-08 22:00 UTCEPSS rescoreEPSS 13% · 96th percentile
  24. 2026-09-08 02:28 UTCEG score recompute
  25. 2026-09-08 02:28 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  26. 2026-09-07 16:01 UTCEPSS rescoreEPSS 13% · 96th percentile
  27. 2026-09-06 13:54 UTCEG score recompute
  28. 2026-09-06 13:54 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  29. 2026-09-06 13:47 UTCEPSS rescoreEPSS 13% · 96th percentile
  30. 2026-09-05 21:37 UTCEG score recompute
  31. 2026-09-05 21:37 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  32. 2026-09-04 05:06 UTCEPSS rescoreEPSS 13% · 96th percentile
  33. 2026-09-02 14:12 UTCEPSS rescoreEPSS 13% · 96th percentile
  34. 2026-09-01 13:53 UTCEPSS rescoreEPSS 13% · 96th percentile
  35. 2026-09-01 04:39 UTCEPSS rescoreEPSS 13% · 96th percentile
  36. 2026-08-30 19:17 UTCEPSS rescoreEPSS 13% · 96th percentile
  37. 2026-08-30 18:02 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  38. 2026-08-30 05:57 UTCEG score recompute
  39. 2026-08-30 05:57 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  40. 2026-08-30 01:22 UTCEPSS rescoreEPSS 13% · 96th percentile
  41. 2026-08-28 21:41 UTCEPSS rescoreEPSS 13% · 96th percentile
  42. 2026-08-27 21:38 UTCEG score recompute
  43. 2026-08-27 21:38 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  44. 2026-08-27 14:25 UTCEPSS rescoreEPSS 13% · 96th percentile
  45. 2026-08-27 00:32 UTCEG score recompute
  46. 2026-08-27 00:32 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  47. 2026-08-26 14:46 UTCEPSS rescoreEPSS 3.5% · 88th percentile
  48. 2026-08-26 02:46 UTCEG score recompute
  49. 2026-08-26 02:46 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  50. 2026-08-25 13:49 UTCEPSS rescoreEPSS 3.5% · 88th percentile
  51. 2026-08-25 09:46 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  52. 2026-08-24 20:09 UTCEG score recompute
  53. 2026-08-24 20:09 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  54. 2026-08-24 03:52 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  55. 2026-08-23 15:46 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  56. 2026-08-23 03:42 UTCEG score recompute
  57. 2026-08-23 03:41 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  58. 2026-08-23 00:19 UTCEPSS rescoreEPSS 3.5% · 88th percentile
  59. 2026-08-22 15:36 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  60. 2026-08-22 03:29 UTCEG score recompute
  61. 2026-08-22 03:29 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  62. 2026-08-21 23:49 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  63. 2026-08-21 15:07 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  64. 2026-08-21 03:02 UTCEG score recompute
  65. 2026-08-21 03:02 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  66. 2026-08-20 22:55 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  67. 2026-08-20 14:47 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  68. 2026-08-20 01:28 UTCEG score recompute
  69. 2026-08-20 01:28 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  70. 2026-08-19 17:03 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  71. 2026-08-19 10:57 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  72. 2026-08-18 22:52 UTCEG score recompute
  73. 2026-08-18 22:52 UTCGHSA enrichmentGHSA-jjq9-3x6f-75pj · GitHub severity HIGH · GitHub CVSS 7.2
  74. 2026-08-18 13:48 UTCEPSS rescoreEPSS 1.1% · 63rd percentile

Publicly available exploits

(4 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 1 Exploit-DB entry, 1 GitHub PoC), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. No fix is confirmed yet, so defenders should restrict or isolate affected systems accordingly until one is published.

  • Metasploitauxiliary/gather/wp_planyo_lfi_cve_2026_3576✓ verified
    Published Aug 26, 2026

    Wordpress Planyo Online Reservation System Arbitrary File Read (CVE-2026-3576)

    Open source ↗
  • Nucleihttp/cves/2026/CVE-2026-3576.yaml
    Published Aug 19, 2026

    Planyo Online Reservation System <= 3.0 - Arbitrary File Read

    Open source ↗
  • Exploit-DBEDB-52636
    Published Aug 11, 2026

    Planyo_Online_Reservation_System 3.0 - Arbitrary File Read via SSRF

    Open source ↗
  • GitHub PoCanirbala98/CVE-2026-3576
    Published Jul 12, 2026

    Proof of Concept exploit for CVE-2026-3576

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-3576?
CVE-2026-3576 is a high-severity vulnerability; its CVE record was published on July 11, 2026. 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.…
When was the CVE record for CVE-2026-3576 published?
The CVE record for CVE-2026-3576 was published on July 11, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 13, 2026; the record at its source may have been updated since.
Is CVE-2026-3576 actively exploited?
CVE-2026-3576 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 8.8% probability of exploitation in the next 30 days (95th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-3576?
CVE-2026-3576 has a CVSS base score of 7.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-3576?
No fix for CVE-2026-3576 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (Wordfence) lists xtreeme Planyo online reservation system versions up to and including 3.0 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-3576 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-3576

Explore →

Is Your Infrastructure Affected by CVE-2026-3576?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs