CVE-2025-9627

Run Log <= 1.7.10 - Cross-Site Request Forgery to Settings Update

2025-09-10 18:53

Strategic Overview

Status: Patched in 1.7.11
Affected Plugin: Run Log
Affected Version: <= 1.7.10
CVSS: 4.3Medium
Weakness type: CWE-352 · Cross-Site Request Forgery (CSRF)
CVE: CVE-2025-9627

At a glance

CVE-2025-9627 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Run Log WordPress plugin, affecting versions <= 1.7.10. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.7.11; sites on affected versions should update now. Disclosed September 2025, reported by Sandeep Kambhampati.

Vulnerability Overview

The Run Log plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.7.10. This is due to missing or incorrect nonce validation on the oirl_plugin_options function. This makes it possible for unauthenticated attackers to modify plugin settings including distance units, pace display preferences, style themes, and display positions via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Run Log <= 1.7.10 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Run Log the fix is 1.7.11: builds <= 1.7.10 are affected, anything from 1.7.11 onward is not.

Remediation

Update to version 1.7.11, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Run Log: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Run Log 1.7.11 closes this, and updating the plugin is the step that ends it.

Firewall
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-9627 https://www.wordfence.com/threat-intel/vulnerabilities/id/8b9ba35b-5ef8-4170-97f4-400fe9bd3af2 https://nvd.nist.gov/vuln/detail/CVE-2025-9627

CVSS Vector

4.3

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

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionRequired
ScopeUnchanged
ConfidentialityNone
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/