CVE-2026-9731: CWE-352 Cross-Site Request Forgery (CSRF) in wpkuf Wp Js Detect
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.
AI Analysis
Technical Summary
CVE-2026-9731 describes a CSRF vulnerability in the Wp Js Detect WordPress plugin affecting all versions up to 1.0.9. The root cause is missing or incorrect nonce validation on the plugin_settings function, which handles updates to notification text and CSS settings. An attacker can exploit this by tricking an authenticated site administrator into submitting a forged request, allowing the attacker to inject arbitrary content into these settings. This content is then rendered unescaped on the frontend, which may lead to content injection issues. There is no vendor advisory or patch currently available for this vulnerability.
Potential Impact
An attacker can perform unauthorized updates to the plugin's notification text and CSS settings by exploiting the CSRF vulnerability, potentially injecting arbitrary content that is displayed unescaped on the frontend. This could lead to content injection, which may affect site integrity or user trust. However, the vulnerability does not directly impact confidentiality or availability. The CVSS 3.1 base score is 4.3 (medium severity), reflecting low complexity and no privileges required but requiring user interaction.
Mitigation Recommendations
No official patch or remediation is currently available for this vulnerability. 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.
CVE-2026-9731: CWE-352 Cross-Site Request Forgery (CSRF) in wpkuf Wp Js Detect
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.
CVSS v3.1
Score 4.3medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-9731 describes a CSRF vulnerability in the Wp Js Detect WordPress plugin affecting all versions up to 1.0.9. The root cause is missing or incorrect nonce validation on the plugin_settings function, which handles updates to notification text and CSS settings. An attacker can exploit this by tricking an authenticated site administrator into submitting a forged request, allowing the attacker to inject arbitrary content into these settings. This content is then rendered unescaped on the frontend, which may lead to content injection issues. There is no vendor advisory or patch currently available for this vulnerability.
Potential Impact
An attacker can perform unauthorized updates to the plugin's notification text and CSS settings by exploiting the CSRF vulnerability, potentially injecting arbitrary content that is displayed unescaped on the frontend. This could lead to content injection, which may affect site integrity or user trust. However, the vulnerability does not directly impact confidentiality or availability. The CVSS 3.1 base score is 4.3 (medium severity), reflecting low complexity and no privileges required but requiring user interaction.
Mitigation Recommendations
No official patch or remediation is currently available for this vulnerability. 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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-05-27T17:24:04.304Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a4de430c9d9e3dbe38c3c21
Added to database: 07/08/2026, 05:46:24 UTC
Last enriched: 07/15/2026, 12:20:25 UTC
Last updated: 08/22/2026, 10:52:11 UTC
Views: 75
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.