Alone < 7.8.5 - Unauthenticated Remote Code Execution
Strategic Overview
- Status
- Patched in 7.8.5
- Affected Theme
- Alone – Charity Multipurpose Non-profit WordPress Theme
- Affected Version
< 7.8.5- CVSS
- 9.8Critical
- Weakness type
- CWE-94 · Improper Control of Generation of Code ('Code Injection')
- CVE
CVE-2025-54019
At a glance
CVE-2025-54019 is a critical-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the Alone WordPress theme, affecting versions < 7.8.5. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 7.8.5; sites on affected versions should update now. Disclosed August 2025, reported by Tran Nguyen Bao Khanh.
Vulnerability Overview
The Alone theme for WordPress is vulnerable to Remote Code Execution in versions up to 7.8.5. This is due to insufficient validation of user supplied input before it is executed. This makes it possible for unauthenticated attackers to execute arbitrary 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 privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-94: Improper Control of Generation of Code ('Code Injection')
Reaching this weakness in Alone < 7.8.5 takes no account at all. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.
The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For Alone the fix is 7.8.5: builds < 7.8.5 are affected, anything from 7.8.5 onward is not.
Remediation
Update to version 7.8.5, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: 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. None of that substitutes for the fix: Alone 7.8.5 closes this, and updating the theme is the step that ends it.
- Firewall
- Scanner
- Login Security
External References
Related records
Same weakness class
Other vulnerabilities in Alone – Charity Multipurpose Non-profit WordPress Theme
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C