CVE-2025-0767: WP Activity Log 5.3.2 - Insecure deserialization
First published: Thu Feb 27 2025(Updated: )
WP Activity Log 5.3.2 was found to be vulnerable. Unvalidated user input is used directly in an unserialize function in myapp/classes/Writers/class-csv-writer.php.
Credit: help@fluidattacks.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| WP Activity Log |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2025-0767?
CVE-2025-0767 has been rated as a high severity vulnerability due to its potential exploitation of unserialized user input.
How do I fix CVE-2025-0767?
To fix CVE-2025-0767, update the WP Activity Log plugin to the latest version where the vulnerability has been addressed.
What impact does CVE-2025-0767 have on my website's security?
CVE-2025-0767 allows attackers to exploit unvalidated user input, potentially leading to remote code execution or data manipulation.
Which versions of WP Activity Log are affected by CVE-2025-0767?
CVE-2025-0767 affects WP Activity Log versions prior to 5.3.2.
Is there a workaround for CVE-2025-0767 if I cannot update immediately?
As a temporary workaround for CVE-2025-0767, remove or disable the WP Activity Log plugin until you can update to a secure version.
- collector/nvd-api
- source/NVD
- agent/last-modified-date
- agent/severity
- agent/author
- agent/references
- agent/weakness
- agent/source
- agent/type
- agent/description
- agent/first-publish-date
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/title
- agent/guess-ai
- agent/software-canonical-lookup
- agent/softwarecombine
- agent/tags
- vendor/wp activity log
- canonical/wp activity log