MainWP Child <= 4.1.7.1 - SQL Injection via orderby, order Parameters
Strategic Overview
- Status
- Patched in 4.1.8
- Affected Version
< 4.1.8- CVSS
- 7.2High
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2021-24877
At a glance
CVE-2021-24877 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the MainWP Child WordPress plugin, affecting versions < 4.1.8. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 4.1.8; sites on affected versions should update now. Disclosed October 2021, reported by ZhongFu Su.
Vulnerability Overview
The MainWP Child WordPress plugin before 4.1.8 does not validate the orderby and order parameter before using them in a SQL statement, leading to an SQL injection exploitable by high privilege users such as admin when the Backup and Staging by WP Time Capsule plugin is installed
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Reaching this weakness in MainWP Child < 4.1.8 takes a caller who can reach the endpoint. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For MainWP Child the fix is 4.1.8: builds < 4.1.8 are affected, anything from 4.1.8 onward is not.
Remediation
Update to version 4.1.8, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to MainWP Child: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: MainWP Child 4.1.8 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in MainWP Child – Securely Connects to the MainWP Dashboard to Manage Multiple Sites
- 9.8MainWP Child Authentication Bypass
- 8.3MainWP Child < 3.4.5 Authentication Bypass
- 8.1CVE-2024-10783: MainWP Child Unauthenticated Privilege Escalation
CVE-2024-10783 - 7.3MainWP Dashboard and MainWP Child <= 2.0.22 Unspecified Vulnerability
- 6.1MainWP Child <= 2.0.27 Multiple Cross-Site Scripting
- 5.9CVE-2023-3132: MainWP Child <= 4.4.1.1 Information Disclosure
CVE-2023-3132 - 5.3CVE-2026-27366: MainWP Child Missing Authorization
CVE-2026-27366
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C