Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-5932: CWE-352 Cross-Site Request Forgery (CSRF) in coolrunner Homerunner

0
Medium
VulnerabilityCVE-2025-5932cvecve-2025-5932cwe-352
Published: Thu Jun 26 2025 (06/26/2025, 02:22:20 UTC)
Source: CVE Database V5
Vendor/Project: coolrunner
Product: Homerunner

Description

The Homerunner plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.29. This is due to missing or incorrect nonce validation on the main_settings() function. This makes it possible for unauthenticated attackers to update plugin settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 15:42:04 UTC

Technical Analysis

CVE-2025-5932 identifies a Cross-Site Request Forgery (CSRF) vulnerability in the Homerunner plugin for WordPress, versions up to and including 1.0.29. The root cause is the absence or improper implementation of nonce validation in the main_settings() function, which is responsible for handling plugin configuration updates. Nonces in WordPress serve as tokens to verify that requests originate from legitimate users and not from malicious third-party sites. Without proper nonce checks, attackers can craft malicious web pages or links that, when visited or clicked by an authenticated site administrator, cause unintended changes to plugin settings. This vulnerability does not require the attacker to be authenticated but does require the administrator to perform an action such as clicking a link, making it a user interaction-based attack. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N) indicates network attack vector, low attack complexity, no privileges required, user interaction required, unchanged scope, no confidentiality or availability impact, and limited integrity impact. While the vulnerability does not expose sensitive data or cause denial of service, unauthorized changes to plugin settings could weaken site security or functionality, potentially leading to further compromise. No patches or exploits are currently documented, but the risk remains significant for sites using this plugin without mitigation.

Potential Impact

The primary impact of this vulnerability is unauthorized modification of the Homerunner plugin settings by an attacker who can trick a site administrator into clicking a malicious link. This can lead to degraded site security posture, misconfiguration, or enabling of malicious features within the plugin. Although confidentiality and availability are not directly affected, integrity is compromised, which could be leveraged as a foothold for further attacks such as privilege escalation or persistent backdoors. Organizations relying on Homerunner for critical WordPress functionality may experience operational disruptions or reputational damage if attackers exploit this flaw. The attack requires user interaction but no authentication, increasing the attack surface. Given WordPress's widespread use globally, many websites could be exposed, especially those with less security awareness or lacking multi-factor authentication for administrators. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as exploit code could be developed rapidly once the vulnerability is public.

Mitigation Recommendations

To mitigate this vulnerability, organizations should immediately update the Homerunner plugin once a patch is released that properly implements nonce validation in the main_settings() function. Until an official patch is available, administrators should restrict access to the WordPress admin panel to trusted networks or IP addresses to reduce exposure. Implementing multi-factor authentication (MFA) for administrator accounts can reduce the risk of successful exploitation. Additionally, administrators should be trained to recognize and avoid clicking suspicious links, especially those received via email or untrusted sources. Web Application Firewalls (WAFs) can be configured to detect and block suspicious POST requests targeting the plugin’s settings endpoints. Regular security audits and monitoring of plugin settings for unauthorized changes can help detect exploitation attempts early. Finally, disabling or removing unused plugins like Homerunner reduces the attack surface.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-06-09T15:05:07.647Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 685cb6e0e230f5b234861d93

Added to database: 6/26/2025, 2:56:32 AM

Last enriched: 2/27/2026, 3:42:04 PM

Last updated: 3/26/2026, 10:07:37 AM

Views: 137

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses