Live › vulnerability › CVE-2026-104769
Go to dashboardThe Debloat WordPress plugin up to and including 1.3.0 fails to sanitize the 's' parameter, allowing directory traversal. An attacker can read arbitrary files on the server, which may contain sensitive data such as configuration secrets.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Sites running Debloat version or earlier with the Optimize CSS feature enabled are exposed, since the sources say that setting must be active for the traversal to be reachable. Sites that do not use the plugin, or that have Optimize CSS disabled, are not affected according to the sources.
1.3.0No product ranges from the sources yet.
wp plugin get debloat (the exact slug is unknown from the sources).1.3.0 or remove it. The sources do not name the fixed release.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The Debloat – Remove Unused CSS, Optimize JS plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 1.3.0 via the 's' parameter parameter. This makes it possible for authenticated attackers, with administrator-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information. Exploitation requires that the site administrator has enabled the Optimize CSS feature (with the default Inline Google Fonts option active), but once that condition is met the attack is trivially triggered by an unauthenticated visitor with a single crafted GET request to the public search URL.
This page as .md · .json · in your agent: get_signal("CVE-2026-104769")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.