Authenticated code execution via local file inclusion
Published Oct 23, 2024 · Updated May 12, 2026
Local file inclusion in Qode Interactive Qi Blocks 1.3.2 and earlier allows remote authenticated users to execute uploaded PHP code. Public advisories do not identify the affected function or parameter; they state only that an attacker-controlled file path reaches a PHP include operation. Contributor-level WordPress access is required, and code execution depends on placing executable content in a server file that the plugin can include.
Summary
What happened
Local file inclusion in Qode Interactive Qi Blocks 1.3.2 and earlier allows remote authenticated users to execute uploaded PHP code. Public advisories do not identify the affected function or parameter; they state only that an attacker-controlled file path reaches a PHP include operation. Contributor-level WordPress access is required, and code execution depends on placing executable content in a server file that the plugin can include.
The record
- CVE
- CVE-2024-49690
- Published
- Oct 23, 2024
- Updated
- May 12, 2026
- Vendor
- Qode Interactive
- Product
- Qi Blocks
- Classifications
- CWE-98, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 23, 2024CVE publishedPublication date reported by the CVE source.
- May 12, 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.2
- Affected versionversion=0 <=1.3.2 changes=[{"at":"1.3.3","status":"unaffected"}]
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