Critical security advisoryCriticalFlagged by our vulnerability database: PHP2Shell is on CISA’s exploited list. Most WordPress hosting runs PHP. See if your site is affectedFlagged by our vulnerability database: PHP2Shell is being exploited. DetailsExploited: PHP2Shell. Check your site
HuttenlocherTechnologies
Updated 3 h ago

Vulnerability database

Every flaw the U.S. government’s cybersecurity agency (CISA) has confirmed attackers are using, plus the new WordPress plugin and theme bugs published each day, sorted by what they mean for a small business. We refresh it twice a day. If you see something your website or office runs, tell us.

1,764exploited flaws on CISA’s list
35added in the last 30 days
479new WordPress flaws this week
390,525entries in the database

27 results

  • Oct 24, 2026W3 Total Cache: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVE-2026-114178 · WordPress plugins & themes · reported by PatchstackHigh 7.1

    Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Bold Grid W3 Total Cache w3-total-cache allows Stored XSS.This issue affects W3 Total Cache: from n/a through 2.10.7.

    Product
    W3 Total Cache
    Affected
    up to 2.10.7
    What to do
    Affects up to 2.10.7. Update W3 Total Cache to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Oct 10, 2026W3 Total Cache: Does not confine a media-import file copy to the document rootCVE-2026-107321 · WordPress plugins & themes · reported by WPScanMedium 5.4

    The W3 Total Cache WordPress plugin before 2.10.6 does not confine a media-import file copy to the document root, nor enforce an effective file-type restriction on it, allowing users with the Author role or higher to plant content that, once an administrator runs the import, copies an arbitrary server-readable file into a publicly served directory, exposing it to unauthenticated retrieval.

    Product
    W3 Total Cache
    Fixed in
    2.10.6
    What to do
    Update W3 Total Cache to 2.10.6 or newer.
  • Oct 2, 2026W3 Total Cache: Stored Cross-Site ScriptingCVE-2026-87920 · WordPress plugins & themes · reported by WordfenceHigh 7.2

    The W3 Total Cache plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content via Output-Buffer Regex Rewrite in all versions up to, and including, 2.10.6 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This vulnerability is only exploitable when the 'Remove query strings from static resources' option is enabled in W3 Total Cache, as mutate_url() must strip the '?' delimiter and everything following it — including the closing quote of the outer attribute — to break the attribute boundary.

    Product
    W3 Total Cache
    Affected
    up to 2.10.6
    What to do
    Affects up to 2.10.6. Update W3 Total Cache to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Sep 5, 2026W3 Total Cache: Stored Cross-Site ScriptingCVE-2026-78438 · WordPress plugins & themes · reported by WordfenceHigh 7.2

    The W3 Total Cache plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content via LazyLoad Background Mutator in all versions up to, and including, 2.10.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires the "Lazy Load Images" feature with "Process background images" to be enabled, and the malicious comment to be approved by a moderator before execution is triggered.

    Product
    W3 Total Cache
    Affected
    up to 2.10.5
    What to do
    Affects up to 2.10.5. Update W3 Total Cache to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Aug 19, 2026W3 Total Cache: Does not properly validate the request path it uses to build cache file namesCVE-2026-18051 · WordPress plugins & themes · reported by WPScanCritical 10

    The W3 Total Cache WordPress plugin before 2.10.5 does not properly validate the request path it uses to build cache file names, allowing unauthenticated attackers to write a file into any existing directory on the server, inside or outside the web root, overwriting whatever occupies the target name. On Apache, the same flaw overwrites the site's .htaccess files, which breaks the site and can strip hardening rules that other security measures rely on.

    Product
    W3 Total Cache
    Fixed in
    2.10.5
    What to do
    Update W3 Total Cache to 2.10.5 or newer.
  • Aug 13, 2026W3 Total Cache: Stored Cross-Site ScriptingCVE-2026-18109 · WordPress plugins & themes · reported by WordfenceHigh 7.2

    The W3 Total Cache plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Author Name in all versions up to, and including, 2.10.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This vulnerability is only exploitable when the Lazy Load Images feature of W3 Total Cache is enabled, as the unsafe re-emission occurs exclusively within the LazyLoad mutator's img tag rewriting step.

    Product
    W3 Total Cache
    Affected
    up to 2.10.3
    What to do
    Affects up to 2.10.3. Update W3 Total Cache to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Aug 6, 2026Unauthenticated Path Traversal in W3 Total Cache <= 2.10.2 versions.CVE-2026-66695 · WordPress plugins & themes · reported by PatchstackMedium 6.5

    Unauthenticated Path Traversal in W3 Total Cache <= 2.10.2 versions.

    Affected
    up to 2.10.2
    What to do
    Affects up to 2.10.2. Update the plugin to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jul 11, 2026W3 Total Cache: Directory TraversalCVE-2026-9282 · WordPress plugins & themes · reported by WordfenceHigh 7.5

    The W3 Total Cache plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 2.9.4 via the setupSources function. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information. Exploitation requires enabling manual minify mode and supplying a manual-format minify filename so that the hash is empty and the f_array[] entries are not overwritten before reaching setupSources().

    Product
    W3 Total Cache
    Affected
    up to 2.9.4
    What to do
    Affects up to 2.9.4. Update W3 Total Cache to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jul 2, 2026Unauthenticated Arbitrary Code Execution in W3 Total Cache <= 2.9.4 versions.CVE-2026-57623 · WordPress plugins & themes · reported by PatchstackCritical 9

    Unauthenticated Arbitrary Code Execution in W3 Total Cache <= 2.9.4 versions.

    What to do
    Update the plugin to the newest version.
  • Jun 17, 2026Author Broken Access Control in W3 Total Cache <= 2.9.1 versions.CVE-2026-39595 · WordPress plugins & themes · reported by PatchstackMedium 4.7

    Author Broken Access Control in W3 Total Cache <= 2.9.1 versions.

    Affected
    up to 2.9.1
    What to do
    Affects up to 2.9.1. Update the plugin to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Apr 2, 2026W3 Total Cache: Information exposureCVE-2026-5032 · WordPress plugins & themes · reported by WordfenceHigh 7.5

    The W3 Total Cache plugin for WordPress is vulnerable to information exposure in all versions up to, and including, 2.9.3. This is due to the plugin bypassing its entire output buffering and processing pipeline when the request's User-Agent header contains "W3 Total Cache", which causes raw mfunc/mclude dynamic fragment HTML comments — including the W3TC_DYNAMIC_SECURITY security token — to be rendered in the page source. This makes it possible for unauthenticated attackers to discover the value of the W3TC_DYNAMIC_SECURITY constant by sending a crafted User-Agent header to any page that contains developer-placed dynamic fragment tags, granted the site has the fragment caching feature enabled. With the leaked W3TC_DYNAMIC_SECURITY token, an attacker can craft valid mfunc tags to execute arbitrary PHP code on the server, achieving remote code execution.

    Product
    W3 Total Cache
    Affected
    up to 2.9.3
    What to do
    Affects up to 2.9.3. Update W3 Total Cache to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Mar 5, 2026W3 Total Cache: Improper Validation of Specified Quantity in InputCVE-2026-27384 · WordPress plugins & themes · reported by PatchstackCritical 9

    Improper Validation of Specified Quantity in Input vulnerability in BoldGrid W3 Total Cache w3-total-cache allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects W3 Total Cache: from n/a through <= 2.9.1.

    Product
    W3 Total Cache
    Affected
    up to 2.9.1
    What to do
    Affects up to 2.9.1. Update W3 Total Cache to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Nov 17, 2025W3 Total Cache: Is vulnerable to command injection via the _parse_dynamic_mfunc functionCVE-2025-9501 · WordPress plugins & themes · reported by WPScanCritical 9

    The W3 Total Cache WordPress plugin before 2.8.13 is vulnerable to command injection via the _parse_dynamic_mfunc function, allowing unauthenticated users to execute PHP commands by submitting a comment with a malicious payload to a post.

    Product
    W3 Total Cache
    Fixed in
    2.8.13
    What to do
    Update W3 Total Cache to 2.8.13 or newer.
  • Jan 14, 2025W3 Total Cache: Unauthorized access of dataCVE-2024-12365 · WordPress plugins & themes · reported by WordfenceHigh 8.5

    The W3 Total Cache plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the is_w3tc_admin_page function in all versions up to, and including, 2.8.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to obtain the plugin's nonce value and perform unauthorized actions, resulting in information disclosure, service plan limits consumption as well as making web requests to arbitrary locations originating from the web application that can be used to query information from internal services, including instance metadata on cloud-based applications.

    Product
    W3 Total Cache
    Affected
    up to 2.8.1
    What to do
    Affects up to 2.8.1. Update W3 Total Cache to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jan 14, 2025W3 Total Cache: Information ExposureCVE-2024-12008 · WordPress plugins & themes · reported by WordfenceMedium 5.3

    The W3 Total Cache plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 2.8.1 through the publicly exposed debug log file. This makes it possible for unauthenticated attackers to view potentially sensitive information in the exposed log file. For example, the log file may contain nonce values that can be used in further CSRF attacks. Note: the debug feature must be enabled for this to be a concern, and it is disabled by default.

    Product
    W3 Total Cache
    Affected
    up to 2.8.1
    What to do
    Affects up to 2.8.1. Update W3 Total Cache to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jan 14, 2025W3 Total Cache: Unauthorized modification of dataCVE-2024-12006 · WordPress plugins & themes · reported by WordfenceMedium 5.3

    The W3 Total Cache plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on several functions in all versions up to, and including, 2.8.1. This makes it possible for unauthenticated attackers to deactivate the plugin as well as activate and deactivate plugin extensions.

    Product
    W3 Total Cache
    Affected
    up to 2.8.1
    What to do
    Affects up to 2.8.1. Update W3 Total Cache to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Sep 24, 2024W3 Total Cache: Sensitive Information ExposureCVE-2023-5359 · WordPress plugins & themes · reported by WordfenceLow 3.7

    The W3 Total Cache plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 2.7.5 via Google OAuth API secrets stored in plaintext in the publicly visible plugin source. This can allow unauthenticated attackers to impersonate W3 Total Cache and gain access to user account information in successful conditions. This would not impact the WordPress users site in any way.

    Product
    W3 Total Cache
    Affected
    up to 2.7.5
    What to do
    Affects up to 2.7.5. Update W3 Total Cache to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jul 19, 2021W3 Total Cache: Was affected by a reflected Cross-Site Scripting (XSS) issue within the "extension" parameter in the Extensions dashboardCVE-2021-24452 · WordPress plugins & themes · reported by WPScanMedium 6.1

    The W3 Total Cache WordPress plugin before 2.1.5 was affected by a reflected Cross-Site Scripting (XSS) issue within the "extension" parameter in the Extensions dashboard, when the 'Anonymously track usage to improve product quality' setting is enabled, as the parameter is output in a JavaScript context without proper escaping. This could allow an attacker, who can convince an authenticated admin into clicking a link, to run malicious JavaScript within the user's web browser, which could lead to full site compromise.

    Product
    W3 Total Cache
    Fixed in
    2.1.5
    What to do
    Update W3 Total Cache to 2.1.5 or newer.
  • Jul 19, 2021W3 Total Cache: Was vulnerable to a reflected Cross-Site Scripting (XSS) security vulnerability within the "extension" parameter in the Extensions dashboardCVE-2021-24436 · WordPress plugins & themes · reported by WPScanMedium 6.1

    The W3 Total Cache WordPress plugin before 2.1.4 was vulnerable to a reflected Cross-Site Scripting (XSS) security vulnerability within the "extension" parameter in the Extensions dashboard, which is output in an attribute without being escaped first. This could allow an attacker, who can convince an authenticated admin into clicking a link, to run malicious JavaScript within the user's web browser, which could lead to full site compromise.

    Product
    W3 Total Cache
    Fixed in
    2.1.4
    What to do
    Update W3 Total Cache to 2.1.4 or newer.
  • Jul 12, 2021W3 Total Cache: Did not sanitise or escape some of its CDN settingsCVE-2021-24427 · WordPress plugins & themes · reported by WPScanMedium 4.8

    The W3 Total Cache WordPress plugin before 2.1.3 did not sanitise or escape some of its CDN settings, allowing high privilege users to use JavaScript in them, which will be output in the page, leading to an authenticated Stored Cross-Site Scripting issue

    Product
    W3 Total Cache
    Fixed in
    2.1.3
    What to do
    Update W3 Total Cache to 2.1.3 or newer.
  • Feb 12, 2020WordPress W3 Total Cache Plugin 0.9.2.8 has a Remote PHP Code Execution VulnerabilityCVE-2013-2010 · WordPress plugins & themes · reported by Red HatCritical 9.8

    WordPress W3 Total Cache Plugin 0.9.2.8 has a Remote PHP Code Execution Vulnerability

    What to do
    Update the plugin to the newest version.
  • Nov 22, 2019W3 Total Cache before 0.9.2.5 exposes sensitive cached database information which allows remote attackers to download this information via their hash keys.CVE-2012-6079 · Other software · W3 · reported by Red HatHigh 7.5

    W3 Total Cache before 0.9.2.5 exposes sensitive cached database information which allows remote attackers to download this information via their hash keys.

    Product
    Total Cache
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 22, 2019W3 Total Cache before 0.9.2.5 generates hash keys insecurely which allows remote attackers to predict the values of the hashes.CVE-2012-6078 · Other software · W3 · reported by Red HatHigh 7.5

    W3 Total Cache before 0.9.2.5 generates hash keys insecurely which allows remote attackers to predict the values of the hashes.

    Product
    Total Cache
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 22, 2019W3 Total Cache before 0.9.2.5 allows remote attackers to retrieve password hash information due to insecure storage of database cache files.CVE-2012-6077 · Other software · W3 · reported by Red HatHigh 7.5

    W3 Total Cache before 0.9.2.5 allows remote attackers to retrieve password hash information due to insecure storage of database cache files.

    Product
    Total Cache
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 1, 2019pub/sns.php in the W3 Total Cache plugin before 0.9.4 for WordPress allows remote attackers to read arbitrary files via the SubscribeURL field in SubscriptionCoCVE-2019-6715 · WordPress plugins & themes · reported by MITREHigh 7.5

    pub/sns.php in the W3 Total Cache plugin before 0.9.4 for WordPress allows remote attackers to read arbitrary files via the SubscribeURL field in SubscriptionConfirmation JSON data.

    Product
    pub/sns.php in the W3 Total Cache
    Fixed in
    0.9.4
    What to do
    Update pub/sns.php in the W3 Total Cache to 0.9.4 or newer.
  • Dec 24, 2014The W3 Total Cache plugin before 0.9.4.1 for WordPress does not properly handle empty nonces, which allows remote attackers to conduct cross-site request forgerCVE-2014-9414 · WordPress plugins & themes · reported by MITREMedium 6.8

    The W3 Total Cache plugin before 0.9.4.1 for WordPress does not properly handle empty nonces, which allows remote attackers to conduct cross-site request forgery (CSRF) attacks and hijack the authentication of administrators for requests that change the mobile site redirect URI via the mobile_groups[*][redirect] parameter and an empty _wpnonce parameter in the w3tc_mobile page to wp-admin/admin.php.

    Product
    W3 Total Cache
    Fixed in
    0.9.4.1
    What to do
    Update W3 Total Cache to 0.9.4.1 or newer.
  • Dec 19, 2014Cross-site scripting (XSS) vulnerability in the W3 Total Cache plugin before 0.9.4.1 for WordPress, when debug mode is enabled, allows remote attackers to injecCVE-2014-8724 · WordPress plugins & themes · reported by MITREMedium 4.3

    Cross-site scripting (XSS) vulnerability in the W3 Total Cache plugin before 0.9.4.1 for WordPress, when debug mode is enabled, allows remote attackers to inject arbitrary web script or HTML via the "Cache key" in the HTML-Comments, as demonstrated by the PATH_INFO to the default URI.

    Product
    Cross-site scripting (XSS) vulnerability in the W3 Total Cache
    Fixed in
    0.9.4.1
    What to do
    Update Cross-site scripting (XSS) vulnerability in the W3 Total Cache to 0.9.4.1 or newer.

Where this comes from: the exploited list is CISA’s Known Exploited Vulnerabilities catalog. Everything else is the whole National Vulnerability Database, where each record is published by the team that found the bug (Wordfence, Patchstack, WPScan, the vendors themselves and others); we show who. Exploit odds are FIRST’s EPSS, updated daily. Titles and categories are ours, so check the linked record before acting on a detail. For a write-up of the big ones, see our advisories. Every vendor, and every WordPress plugin and theme with a recorded flaw, also has its own page. All of it is free to reuse as JSON, CSV or RSS.

Weekly security brief

The flaws that hit local websites, every Friday.

One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.

Get in touch

Tell us what you're building.

A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.

01The person who'll do the work writes back
02A short call, then a written plan with the price
03Nothing starts until you say yes
04Hacked or down right now? Call, and we pick up the same day
843-331-6339

Not ready to talk yet? Run the free website check and see what Google sees.

What do you need?
Build
Grow
Protect
Urgent

No newsletter, no sales sequence. Just a reply.