Unauthenticated shortcode execution via unvalidated AJAX input
Published Oct 16, 2024 · Updated Apr 8, 2026
Code injection in ThemeHunk WP Popup Builder 1.3.5 and earlier allows remote attackers to execute arbitrary shortcodes through an AJAX request. The wp_ajax_nopriv_shortcode_Api_Add handler passes an attacker-controlled shortcode value to do_shortcode without first enforcing authorization. No WordPress account is required, and the resulting behavior depends on the shortcode handlers available on the affected site.
Summary
What happened
Code injection in ThemeHunk WP Popup Builder 1.3.5 and earlier allows remote attackers to execute arbitrary shortcodes through an AJAX request. The wp_ajax_nopriv_shortcode_Api_Add handler passes an attacker-controlled shortcode value to do_shortcode without first enforcing authorization. No WordPress account is required, and the resulting behavior depends on the shortcode handlers available on the affected site.
The record
- CVE
- CVE-2024-9061
- Published
- Oct 16, 2024
- Updated
- Apr 8, 2026
- Vendor
- ThemeHunk
- Product
- WP Popup Builder
- Classifications
- CWE-94, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 16, 2024CVE publishedPublication date reported by the CVE source.
- Apr 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.3.5
What conditions does exploitation require?
What is affected?
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