ChamaWP – Monetize With Donations, Memberships, Crowdfunding, Commissions & Restricted Content < 1.0.13 - Unauthenticated PHP Object Injection
Strategic Overview
- Status
- Patched in 1.0.13
- Affected Plugin
- ChamaWP – Monetize With Donations, Memberships, Crowdfunding, Commissions & Restricted Content
- Affected Version
< 1.0.13- CVSS
- 8.1High
- Weakness type
- CWE-502 · Deserialization of Untrusted Data
- CVE
CVE-2025-15672
At a glance
CVE-2025-15672 is a high-severity Deserialization of Untrusted Data vulnerability in the ChamaWP WordPress plugin, affecting versions < 1.0.13. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.0.13; sites on affected versions should update now. Disclosed August 2026, reported by Khaled Alenazi (Nxploited).
Vulnerability Overview
The ChamaWP – Monetize With Donations, Memberships, Crowdfunding, Commissions & Restricted Content plugin for WordPress is vulnerable to PHP Object Injection in versions up to 1.0.13 via deserialization of untrusted input. This makes it possible for unauthenticated attackers to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, 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-502: Deserialization of Untrusted Data
Reaching this weakness in ChamaWP < 1.0.13 takes no account at all. Deserialization of untrusted data means the application reconstructs objects from input a caller controls, letting the attacker choose which classes get instantiated and what their properties hold.
A workable chain turns deserialization into file writes, deletions or code execution, depending on what the loaded classes do in their magic methods. For ChamaWP the fix is 1.0.13: builds < 1.0.13 are affected, anything from 1.0.13 onward is not.
Remediation
Update to version 1.0.13, 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: ChamaWP 1.0.13 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Login Security
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C