CVE-2026-9731 MEDIUM

CVE-2026-9731: Wp Js Detect <= 1.0.9 - Cross-Site Request Forgery to Plugin Settings Update

Vendor Wpkuf
Product Wp Js Detect
Weakness CWE-352 · CSRF
Published July 8, 2026
Last update July 8, 2026

CVSS base score

4.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

WP JS Detect versions 1.0.9 and earlier are vulnerable to cross-site request forgery (CSRF) attacks. An attacker can craft a malicious webpage that, when visited by a logged-in site administrator, performs unwanted actions on the site without their knowledge. The vulnerability requires the victim to visit the attacker's page while authenticated to WordPress.

What an attacker can do

03Attacker Capabilities

Perform unwanted actions on the site by tricking an authenticated admin into visiting a malicious webpage.

Potential impact on your site

04Site Impact

An attacker can modify site settings or content if an admin visits a malicious link while logged in.

Conditions required to exploit

05Prerequisites

Victim must be logged into WordPress and visit an attacker-controlled page.

Key dates

06Disclosure timeline

July 8, 2026 CVE published
July 8, 2026 Record updated

Related vulnerabilities

08Related CVE