Wp Activity LogWordPress extension · Melapress
CVE-2025-0767
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWP 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe WP Activity Log plugin version 5.3.2 contains a PHP Object Injection vulnerability in the CSV writer class (myapp/classes/Writers/class-csv-writer.php). Unvalidated user-supplied data is passed directly to PHP's unserialize() function, which can be exploited to inject arbitrary PHP objects and potentially achieve remote code execution through magic method invocation chains.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Wp Activity LogWordPress extension
= 5.3.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify plugin installationCheck if the Melapress WP Activity Log plugin is installed in your WordPress environment. Look in the /wp-content/plugins/ directory for a folder containing 'wp-activity-log' or 'melapress', or view installed plugins via the WordPress admin dashboard.Affected if The plugin is present in the WordPress installation
-
Confirm installed versionDetermine the exact version number of the WP Activity Log plugin. In the WordPress admin, go to Plugins > Installed Plugins and locate the version, or inspect the plugin's main PHP file header for the 'Version' field.Affected if Installed version is exactly 5.3.2
-
Locate vulnerable fileCheck for the existence of the file myapp/classes/Writers/class-csv-writer.php within the plugin directory structure. This file contains the vulnerable code path.Affected if The file myapp/classes/Writers/class-csv-writer.php exists in the plugin installation
-
Identify CSV export usageDetermine if the CSV export functionality is accessible. This feature allows administrators to export activity logs in CSV format and is the entry point for the vulnerable unserialize() call.Affected if The CSV export feature is enabled or accessible to users in the plugin
You are affected if WP Activity Log version 5.3.2 is installed with the vulnerable CSV export functionality accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace the unsafe unserialize() call with a secure deserialization method (such as json_decode) after implementing proper input validation, or implement a whitelist approach if PHP deserialization is truly required.
Fix this in Wp Activity Log
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0767 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-0767 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data