Estatik ≤ 4.3.6: Local File Inclusion in a Real-Estate Plugin (CVE-2026-125795, CVSS 9.8)

Running Estatik on your site? Check it against CVE-2026-125795 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your Estatik is in the affected range (≤ 4.3.6), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

Estatik ≤ 4.3.6: Local File Inclusion in a Real-Estate Plugin (CVE-2026-125795, CVSS 9.8)

A plugin that displays property listings has no business deciding which PHP file the server should run next. In Estatik, a WordPress real-estate plugin, improper control of a filename used in an include/require lets an unauthenticated visitor influence that choice — a local file inclusion flaw, CVE-2026-125795, scoring CVSS 9.8. No login is needed, and the files an attacker can reach this way are the server's own.

What Happened

CVE-2026-125795 is a local file inclusion vulnerability (CWE-98: improper control of filename for include/require statements in PHP) in the Estatik WordPress plugin (wordpress.org slug estatik; CNA: Patchstack).

Am I Affected?

Check wp-admin → Plugins for Estatik and its version. At 4.3.6 or below, you are in the affected range. Real-estate sites are exactly the kind of site that leaves a listings plugin installed and untouched for years — if Estatik is on the site at all, check the version before assuming someone updated it.

One honesty note, because it is the whole point of how we cover these: our scanner checks it — the free mini-scan passively reads the version your site announces in Estatik's public readme and flags ≤ 4.3.6 as vulnerable, and a site on 4.3.7 or later earns a clean mark for this CVE. That is a version read only: the scan never sends an inclusion payload, and a version in range proves exposure, not that anyone has exploited it.

What To Do Now

  1. Update Estatik to 4.3.7 or later today. This one has a verified fixed version in the record — use it.
  2. If an affected version was reachable from the internet, review before you relax. Look at web-server and PHP logs around the exposure window for requests you do not recognize, and check for files in uploads or theme directories that should not be there — local file inclusion is often the first step, not the whole attack.
  3. Rotate what an included file could have exposed. If wp-config.php or other configuration files could have been read, the database credentials and salts inside them should be treated as known: rotate them.
  4. Audit admin users. A new administrator you do not recognize is the standard persistence move after a file-inclusion foothold.

The Bigger Lesson

A filename that reaches include or require is not data — it is code selection. Letting request input choose which file PHP loads is handing the visitor a menu of the server's filesystem, and the only safe version of that feature is an allow-list: a fixed set of named templates the code may load, with everything else refused. "Sanitize the path" is how this bug survives code review; "the path can only be one of these five values" is how it dies. When an AI builder or a plugin wires user input into an include, the review question is never "did we clean the input?" It is "can the input name a file we did not intend to offer?" If yes, it is this CVE with a different number.

Related: WordPress Hardening for AI-Built Sites — the standing version of this discipline. How to Check If Your Web App Is Hacked — the follow-up pass if the review finds something you do not recognize.


Running a property site on Estatik? Update to 4.3.7 or later today, then run the free check at preshipit.com/free-scan — it reads the Estatik version your site announces and flags anything at 4.3.6 or below, alongside the rest of your site's outside-visible exposures.

Check Estatik on your own site — free.

Our free WordPress Plugin Vulnerability Checker pulls Estatik's current version from wordpress.org and lists the vulnerabilities our scanner checks for — CVE-2026-125795 included. No scan, no account.

Open the free plugin checker →

The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.

New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.

Running Estatik on your site? Check it against CVE-2026-125795 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your Estatik is in the affected range (≤ 4.3.6), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report