MEDIUM 4.3

CVE-2026-9724: MotorDesk WordPress Plugin CSRF Vulnerability (v1.1.2 and Earlier)

The MotorDesk plugin for WordPress has a cross-site request forgery (CSRF) vulnerability that allows an attacker to trick a site administrator into unwittingly changing the plugin's settings. By crafting a malicious link or webpage, an unauthenticated attacker can alter critical configuration like the search page URI and custom template directory path if they can convince an admin to click a link while logged in. The vulnerability affects all versions up to and including 1.1.2 and requires social engineering but poses a real risk to site integrity and functionality.

Source data · NVD / CISA · public domain

CVSS
3.1 · 4.3 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Weaknesses (CWE)
CWE-352
Affected products
0 configuration(s)
Published / Modified
2026-06-24 / 2026-06-25

NVD description (verbatim)

The MotorDesk plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1.2. This is due to missing or incorrect nonce validation on the motordesk_admin_home function. This makes it possible for unauthenticated attackers to update the plugin's configuration settings, including the search page URI and custom template directory path via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

5 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-9724 is a CSRF vulnerability in the MotorDesk WordPress plugin stemming from inadequate or absent nonce validation in the motordesk_admin_home function. The vulnerability is classified under CWE-352 (Cross-Site Request Forgery). The attack requires an authenticated administrator to be tricked into executing a forged request, but the attacker themselves does not need to be authenticated. Because the vulnerability affects settings updates with limited validation, a successful exploit can redirect the plugin's search functionality or point template loading to attacker-controlled directories, potentially enabling further compromise.

Business impact

A compromised MotorDesk configuration can degrade site functionality, redirect users to attacker-controlled search results, or load malicious templates. This may lead to data theft, malware distribution, or user mistrust. For organizations relying on MotorDesk for site search and content delivery, this represents a risk of operational disruption and reputational damage. The attack surface is low-friction because it relies on social engineering rather than system weaknesses, making user awareness critical.

Affected systems

All versions of the MotorDesk plugin for WordPress up to and including version 1.1.2 are vulnerable. WordPress sites with the MotorDesk plugin installed and administrators who may be targeted by CSRF attacks are at risk. The vulnerability does not require specific WordPress versions or server configurations beyond a standard WordPress installation with the vulnerable plugin active.

Exploitability

Exploitability is straightforward for an attacker with knowledge of the vulnerable endpoint and admin interface, but requires social engineering to succeed. The attacker must craft a forged request and deliver it via a malicious link or embedded form to a logged-in administrator. The CVSS score of 4.3 reflects low confidentiality impact and no availability impact, with integrity limited to plugin configuration. Real-world exploitation likelihood depends on the attacker's ability to social-engineer site admins, which varies by target awareness and email security posture. No known public exploits or active KEV listing currently exist.

Remediation

Update the MotorDesk plugin to a patched version that implements proper nonce validation on the motordesk_admin_home function and other admin functions accepting configuration changes. Verify the patched version details against the official MotorDesk plugin repository or vendor advisory. In the interim, restrict admin access to trusted users, monitor admin activity logs for unauthorized changes, and educate administrators about CSRF attack vectors and the risks of clicking untrusted links while logged in.

Patch guidance

Review the official MotorDesk plugin repository and vendor security advisory for confirmed patched versions released after version 1.1.2. Apply updates immediately upon availability in your WordPress plugin management interface. Before deploying patches to production, test in a staging environment to ensure compatibility with your active themes and other plugins. After patching, verify that search URI and template directory settings remain correct and that no unintended configuration drift occurred during the update.

Detection guidance

Monitor WordPress admin action logs (if logging is enabled via a security plugin) for unexpected changes to MotorDesk settings, including search page URI and custom template directory modifications. Look for POST requests to wp-admin that reference motordesk_admin_home without a corresponding legitimate admin action in session logs. Implement security headers such as SameSite cookies on your WordPress site to reduce CSRF attack surface. Use WordPress security plugins (e.g., Wordfence, Sucuri) that can log and alert on configuration changes, and enable two-factor authentication for admin accounts to raise the friction of social-engineering attacks.

Why prioritize this

Although the CVSS score is moderate (4.3), this vulnerability warrants timely attention because it affects a plugin used to deliver core site functionality (search and templating). The social-engineering barrier is the primary defense; once an admin is compromised via a CSRF attack, legitimate site operations can be disrupted. Organizations with high-value MotorDesk configurations or those in regulated industries should prioritize patching to prevent unauthorized admin settings changes. The lack of KEV listing indicates this is not yet being exploited at scale, providing a window to patch before threats emerge.

Risk score, explained

The CVSS v3.1 score of 4.3 (MEDIUM) reflects a network-accessible attack requiring no privileges but needing user interaction (administrator click), with integrity impact limited to configuration changes and no impact on confidentiality or availability. The risk is material but not critical; the real-world impact depends on the value of the MotorDesk configuration and the likelihood of successful social engineering targeting your admins. Organizations with strict admin workflows and user awareness training will face lower risk than those with less disciplined access practices.

Frequently asked questions

What is a CSRF vulnerability and why does it matter in this context?

CSRF (Cross-Site Request Forgery) exploits the trust a website has in a user's browser. If a WordPress admin is logged in and clicks a malicious link, the attacker's request runs in the admin's context without the admin's knowledge. In the case of MotorDesk, this allows unauthorized changes to search and template settings. Unlike SQL injection or direct code execution, CSRF requires social engineering, but it's effective because admins are often the target of phishing and malicious links.

What versions of MotorDesk are affected?

All versions of the MotorDesk plugin up to and including 1.1.2 are vulnerable. Check your WordPress plugin dashboard to determine your installed version. Versions released after 1.1.2 (if any) should include the security fix; verify against the official MotorDesk repository or the vendor's security advisory for confirmation.

Do I need to be logged in for the attack to work?

Only the WordPress administrator needs to be logged in. The attacker themselves does not need authentication. The attacker creates a crafted link or webpage and tricks the admin into clicking it while already logged into WordPress. This is why user awareness training and suspicious link recognition are important defenses.

Are there any workarounds if I cannot patch immediately?

Yes. Limit administrative access to trusted users only, enforce strong passwords and two-factor authentication on admin accounts, use WordPress security plugins to monitor and alert on settings changes, and educate admins to avoid clicking links from untrusted sources while logged in. However, these are temporary mitigations; patching remains the permanent solution.

This analysis is based on publicly available information current as of the vulnerability publication date (2026-06-24). CVSS scores and severity ratings are provided by the vulnerability source and should be evaluated in the context of your specific environment and risk tolerance. Patch version numbers and availability must be verified against official vendor advisories and the WordPress plugin repository. This information is for defensive security purposes only; any references to exploitation techniques are educational and not intended as offensive instructions. Organizations should conduct their own risk assessment before prioritizing remediation and consult vendor documentation for definitive guidance on patched versions and migration steps. Source: NVD (public-domain), retrieved 2026-07-30. Analysis generated by SEC.co (claude-haiku-4-5).