The Search Exclude plugin for WordPress is vulnerable to unauthorized modification of data due to a insufficient
Source GCVE Database
Not known to be exploited · CVSS 4.3 Medium.
Data as of 18 Nov 2026, 02:28 UTC
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
AI-suggested
Users should monitor the vendor's advisory channels for updates. Until a fix is available, restrict Contributor-level access to trusted users only to reduce risk. No additional mitigation guidance is provided by the vendor.
Description
The Search Exclude plugin for WordPress versions up to and including 2.5.7 has a vulnerability due to insufficient capability checks in the Base::get_rest_permission() method. This flaw allows authenticated users with Contributor-level access or higher to modify plugin settings, including adding arbitrary posts to the search exclusion list. The vulnerability has a medium severity rating with a CVSS score of 4.3. No patch or fix information is provided in the available data.