Subscriber-level code execution via stored eval input
Published Jul 8, 2026 · Updated Jul 8, 2026
Code injection in Total Bounty Widget Logic Visual 1.52 and earlier allows remote authenticated users to execute PHP code via an AJAX request. The widget-logic-update-conditional-tags handler stores the nwlv[cod-tag] value without a capability check or nonce verification, and widget_logic_visual_check_visibility later passes it to eval(). Subscriber-level access is sufficient, so successful exploitation executes attacker-supplied PHP code in the WordPress server context.
Summary
What happened
Code injection in Total Bounty Widget Logic Visual 1.52 and earlier allows remote authenticated users to execute PHP code via an AJAX request. The widget-logic-update-conditional-tags handler stores the nwlv[cod-tag] value without a capability check or nonce verification, and widget_logic_visual_check_visibility later passes it to eval(). Subscriber-level access is sufficient, so successful exploitation executes attacker-supplied PHP code in the WordPress server context.
The record
- CVE
- CVE-2026-14158
- Published
- Jul 8, 2026
- Updated
- Jul 8, 2026
- Vendor
- Total Bounty
- Product
- Widget Logic Visual
- Classifications
- CWE-434, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 8, 2026CVE publishedPublication date reported by the CVE source.
- Jul 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.52
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo