Skip to main content
VulnerabilityPublished

CVE-2026-9731: Wp Js Detect · Cross-Site Request Forgery (CSRF)

Affects Wp Js DetectSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.3 Medium.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 20 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
wpkufWp Js DetectAffected
  • <=1.0.9
Fixed in–

AI-suggested

Users should monitor the vendor's advisory channels for updates. As a temporary mitigation, site administrators should be cautious about clicking on untrusted links while logged into WordPress admin interfaces to avoid CSRF exploitation. Implementing additional CSRF protections such as web application firewalls or custom nonce validation may help reduce risk until an official fix is released.

Description

The Wp Js Detect plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.9. This is due to missing or incorrect nonce validation on the plugin_settings function. This makes it possible for unauthenticated attackers to update the plugin's notification text and CSS settings (wp_non_js_notification_text and wp_non_js_notification_css), injecting arbitrary content that is echoed unescaped on the frontend via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

References

Community reviews

Loading reviews…