CVE-2025-8678

WP Crontrol - 1.17.0 - 1.19.1 - Authenticated (Administrator+) Blind Server-Side Request Forgery

2025-08-21 00:00
Jonas Benjamin Friedli

Strategic Overview

Status
Patched in 1.19.2
Affected Plugin
WP Crontrol
Affected Version
1.17.0 – 1.19.1
CVSS
5.9Medium
Weakness type
CWE-918 · Server-Side Request Forgery (SSRF)
CVE
CVE-2025-8678
View all WP Crontrol vulnerabilities

At a glance

CVE-2025-8678 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the WP Crontrol WordPress plugin, affecting versions 1.17.0 – 1.19.1. It carries a CVSS score of 5.9 (reachable over the network; high confidentiality, integrity impact). Exploitation requires an authenticated account at Administrator level or above. The issue is fixed in version 1.19.2; sites on affected versions should update now. Disclosed August 2025, reported by Jonas Benjamin Friedli.

Vulnerability Overview

The WP Crontrol plugin for WordPress is vulnerable to blind Server-Side Request Forgery in versions 1.17.0 to 1.19.1 via the 'wp_remote_request' function. This makes it possible for authenticated attackers, with Administrator-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity.

CWE-918: Server-Side Request Forgery (SSRF)

WP Crontrol 1.17.0 – 1.19.1 carries this weakness at wp_remote_request, and reaching it takes an account at Administrator level or above. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.

The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For WP Crontrol the fix is 1.19.2: builds 1.17.0 – 1.19.1 are affected, anything from 1.19.2 onward is not.

Remediation

Update to version 1.19.2, or a newer patched version

How does WordSec protect against this?

An attacker needs Administrator access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Crontrol 1.19.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C