Dextaz Ping <= 0.65 - Authenticated (Admin+) Remote Code Execution
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Dextaz Ping
- Affected Version
<= 0.65- CVSS
- 7.2High
- Weakness type
- CWE-77 · Improper Neutralization of Special Elements used in a Command ('Command Injection')
- CVE
CVE-2024-34792
At a glance
CVE-2024-34792 is a high-severity Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in the Dextaz Ping WordPress plugin, affecting versions <= 0.65. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Admin level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed May 2024, reported by Myungju Kim.
Vulnerability Overview
The Dextaz Ping plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 0.65. This makes it possible for authenticated attackers, with administrator-level access and above, to execute code on the server.
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-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Scanner
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C