Verified as of November 21, 2026.

On November 20, 2026, Wordfence Intelligence published and updated a notice for CVE-2026-119114, credited to Jakub Herman. It concerns the WordPress directory plugin WP Fastest Cache (slug wp-fastest-cache) up to and including version 1.5.4, with a fix in 1.5.5. The report describes deletion of directories and files outside the intended WordPress cache area, which can break a website. Wordfence names conditional additional compromise as a possibility, not a confirmed incident, and no exploitation in the wild has been established.

Two scoping points matter. First, the path described by Wordfence does not require the attacker to be logged in. Second, Wordfence states that it requires Custom Permalinks or GeoDirectory to be installed alongside WP Fastest Cache. If you cannot establish whether that combination exists on your site, update anyway.

This is a different issue from CVE-2026-111464, which was fixed in 1.5.4 and covered in our November 3 roundup.

For a shorter summary, read our concise briefing on CVE-2026-119114.

What 1.5.5 changes

The changelog on the WordPress directory confirms that 1.5.5 adds path validation before cache deletion. The same release also changes purge behaviour and reverts a previous blanket rule that prevented caching responses carrying private or non-cacheable HTTP headers.

That second change is why your cache exclusions deserve a deliberate check after the update. Cache exclusions are the pages, URLs or cookies you have told the plugin never to cache, typically login, checkout, cart and account pages. Confirm those, along with any other logged-in or personalized paths, still behave as you intend.

Before you change anything

  • Inventory. In your admin plugin list, confirm the installed WP Fastest Cache version and whether Custom Permalinks or GeoDirectory is present.
  • Protected backup. Take a backup of both files and the database, store it somewhere the site itself cannot overwrite, and confirm that it can actually be restored before you touch cache configuration.
  • Staging. If you maintain a staging copy, apply the update there first with the same plugin set.

Update

Update WP Fastest Cache from the official channel to 1.5.5 or a later patched version. Record the plugin version before and after the update, together with the time of the change, so any later incident or recovery review has a clear reference.

Verify with ordinary owner actions

These are checks you already perform on your own site with your own accounts. There is no need to try to reproduce the reported behaviour.

  • Load a public page, then a normal URL with a campaign parameter, and confirm both render correctly.
  • Edit and publish a page you own, then confirm the change appears after a normal purge.
  • Run through any real permalink and directory listing workflows you rely on, using ordinary content.
  • Compare guest and logged-in views of public pages and of your own account using separate regular browser sessions and harmless staging or test content.
  • Check login, forms and, where relevant, cart or account paths. Coordinate the origin cache and any CDN layer you already control, so one does not serve what the other is meant to exclude.

Confirm the exclusions that are actually configured, not the ones you remember setting.

If something is already wrong

If the site is malfunctioning or content is missing, preserve logs first. Ask your host to assess the scope. Recovery may involve restoring clean content and database data from a trusted protected copy into the patched installation, under your host’s guidance and without reintroducing vulnerable code. Which restore options are available depends on the backups you hold.

If you cannot patch immediately, agree with your maintainer how to pause or replace the affected cache layer while preserving service. Treat that as a holding step, not a permanent mitigation.

Sources