Summary
CVE-2026-13600 is an authentication bypass / improper authentication vulnerability (CWE-287) affecting the AutoNetTV Relay WordPress plugin. The plugin fails to perform any capability or authentication check before setting a WordPress administrator authentication cookie during its scheduled content-synchronization task, allowing an unauthenticated remote attacker to trigger that task and obtain administrator-level session credentials. The issue carries a CVSS v3.1 base score of 8.1 (High).
Technical details
- Root cause: The plugin’s scheduled ("cron") content-synchronization routine sets a WordPress administrator authentication cookie without first verifying the caller’s identity, capability, or session state.
- Trigger conditions: On certain server configurations, an unauthenticated attacker can directly invoke or trigger the scheduled sync task (e.g., by requesting the endpoint/hook responsible for the synchronization), causing the plugin to issue a valid admin auth cookie to the attacker.
- Attack vector: Network — no authentication, privileges, or user interaction are required (AV:N, PR:N, UI:N), though the attack has high complexity (AC:H) since it depends on specific server/task-execution conditions being met.
- Impact: Successful exploitation grants the attacker a WordPress administrator session, resulting in full compromise of confidentiality, integrity, and availability of the affected site (complete site takeover, including content modification, plugin/theme installation, and data exfiltration).
Affected software
- AutoNetTV Relay WordPress plugin — all versions prior to 3.0.14
Severity
- CVSS v3.1 Base Score: 8.1 (High)
- Vector:
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: Upgrade the AutoNetTV Relay plugin to version 3.0.14 or later, which adds the missing authentication/capability checks before the scheduled sync task sets the administrator cookie.
- If unable to patch immediately:
- Temporarily deactivate the AutoNetTV Relay plugin until the update can be applied.
- Restrict or disable access to WordPress cron (
wp-cron.php) execution from untrusted/external sources, and consider moving scheduled task execution to a server-side cron job that is not directly reachable over the network. - Monitor site access and admin logs for unexpected administrator logins or sessions originating from unfamiliar IP addresses, particularly correlated with cron/sync task execution.
- Enforce a Web Application Firewall (WAF) rule set capable of detecting anomalous requests to plugin sync/cron endpoints.

