CVE-2025-32145: WordPress WpEvently plugin <= 4.3.5 - PHP Object Injection vulnerability
First published: Thu Apr 10 2025(Updated: )
Deserialization of Untrusted Data vulnerability in magepeopleteam WpEvently allows Object Injection. This issue affects WpEvently: from n/a through 4.3.5.
Credit: audit@patchstack.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| WpEvently | <=4.3.5 | |
| WordPress WpEvently | <=4.3.5 |
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.
Frequently Asked Questions
What is the severity of CVE-2025-32145?
CVE-2025-32145 is classified as a critical vulnerability due to its potential for remote code execution through object injection.
How do I fix CVE-2025-32145?
To fix CVE-2025-32145, upgrade WpEvently to version 4.3.6 or later to mitigate the deserialization of untrusted data vulnerability.
What versions of WpEvently are affected by CVE-2025-32145?
CVE-2025-32145 affects WpEvently from all versions up to and including 4.3.5.
What is the impact of CVE-2025-32145 on website security?
The impact of CVE-2025-32145 on website security includes the potential for unauthorized access and manipulation of the website, leading to data breaches.
Who can exploit CVE-2025-32145?
CVE-2025-32145 can be exploited by unauthenticated attackers who can send crafted serialized objects to vulnerable WpEvently installations.
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/title
- agent/type
- agent/references
- agent/description
- agent/first-publish-date
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/author
- agent/severity
- agent/last-modified-date
- agent/event
- collector/epss-latest
- source/FIRST
- agent/source
- agent/epss
- agent/tags
- vendor/magepeopleteam
- canonical/wpevently
- vendor/wordpress
- canonical/wordpress wpevently