Contributor-level content injection via undisclosed input handling
Published Jun 4, 2024 · Updated Apr 28, 2026
Content injection in WP Darko Responsive Tabs before 4.0.6 allows remote authenticated users to add arbitrary content to WordPress pages. Published sources do not identify the affected function, input field, or missing neutralization operation, so the exact code-level mechanism is undisclosed. Contributor-level access or higher is required; successful exploitation can alter visible site content for spam or phishing but does not disclose data.
Summary
What happened
Content injection in WP Darko Responsive Tabs before 4.0.6 allows remote authenticated users to add arbitrary content to WordPress pages. Published sources do not identify the affected function, input field, or missing neutralization operation, so the exact code-level mechanism is undisclosed. Contributor-level access or higher is required; successful exploitation can alter visible site content for spam or phishing but does not disclose data.
The record
- CVE
- CVE-2023-45635
- Published
- Jun 4, 2024
- Updated
- Apr 28, 2026
- Vendor
- WP Darko
- Product
- Responsive Tabs
- Classifications
- CWE-80, CAPEC-242, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 4, 2024CVE publishedPublication date reported by the CVE source.
- Apr 28, 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=n/a <4.0.6 changes=[{"at":"4.0.6","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