wpkuf Wp Js Detect Plugin up to 1.0.9 Settings plugin_settings cross-site request forgery

Summaryinfo

A vulnerability classified as problematic has been found in wpkuf Wp Js Detect Plugin up to 1.0.9. This impacts the function plugin_settings of the component Settings Handler. The manipulation of the argument wp_non_js_notification_text/wp_non_js_notification_css leads to cross-site request forgery. This vulnerability is documented as CVE-2026-9731. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in wpkuf Wp Js Detect Plugin up to 1.0.9 and classified as problematic. This issue affects the function plugin_settings of the component Settings Handler. The manipulation of the argument wp_non_js_notification_text/wp_non_js_notification_css with an unknown input leads to a cross-site request forgery vulnerability. Using CWE to declare the problem leads to CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. Impacted is integrity. The summary by CVE is:

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.

The advisory is shared at wordfence.com. The identification of this vulnerability is CVE-2026-9731 since 05/27/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-42173). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• WordPress Plugin

Vendor

• wpkuf

Name

• Wp Js Detect Plugin

Version

• 1.0.0
• 1.0.1
• 1.0.2
• 1.0.3
• 1.0.4
• 1.0.5
• 1.0.6
• 1.0.7
• 1.0.8
• 1.0.9

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion