CVE-2026-116610

MEDIUM CVSS 4.3
Published: 2026-10-28
Modified: 2026-10-28
Enriched via mock
Tenable Plugin

Checking the public Tenable catalog…

AI Threat Summary

CVE-2026-116610 is a moderate vulnerability with a CVSS score of 4.3 affecting the target software. Threat hunters should monitor for exploit attempts and apply vendor patches immediately.

Description

The Clean Login plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 1.20.1 due to a missing capability check on the CleanLogin_Shortcode::get_pages_with_shortcodes() function hooked to the save_post action. This makes it possible for authenticated attackers, with Contributor-level access and above, to overwrite the plugin's cl_login_url/cl_login_id/cl_register_url/cl_register_id/cl_restore_url/cl_restore_id/cl_edit_url/cl_edit_id/cl_change_password_url/cl_change_password_id options with the ID and permalink of a post they themselves authored — simply by embedding the plugin's shortcodes in their own post content.

Attack Chain
1
Reconnaissance

Attacker scans for vulnerable versions using version banners or PoC scanners

2
Initial Access

Attacker triggers CVE-2026-116610 vulnerability with a crafted request or payload

3
Execution

Vulnerability exploited to perform unauthorized actions on the target system

4
Impact

Depending on vulnerability type, attacker achieves data access, service disruption, or code execution

MITRE ATT&CK Techniques
T1190 Exploit Public-Facing Application
Initial Access

Public-facing application vulnerability exploited for initial access

T1203 Exploitation for Client Execution
Execution

Vulnerability exploited to execute attacker-controlled code

Indicators of Compromise
Type Value Description
user_agent Mozilla/5.0 (compatible; exploit/1.0) Generic exploit scanner user agent pattern
url /api/vuln-endpoint?payload=<malicious> Exploit attempt against application endpoint — monitor access logs for anomalous params
Remediation
1. Apply vendor-supplied security patches immediately. 2. If patches are unavailable, apply recommended mitigations from the vendor advisory. 3. Enable WAF rules or IDS signatures to detect exploitation attempts. 4. Monitor logs for indicators of compromise listed above. 5. Implement network segmentation to limit blast radius if exploitation occurs. 6. Subscribe to vendor security advisories for this product.