CVE-2025-32487: WordPress Waymark <= 1.5.2 - Server Side Request Forgery (SSRF) Vulnerability
First published: Wed Apr 09 2025(Updated: )
Server-Side Request Forgery (SSRF) vulnerability in Joe Waymark allows Server Side Request Forgery. This issue affects Waymark: from n/a through 1.5.2.
Credit: audit@patchstack.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Waymark | <=1.5.2 | |
| WordPress Waymark | <=1.5.2 |
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-32487?
CVE-2025-32487 is classified as a critical severity vulnerability due to its potential for exploitation via Server-Side Request Forgery.
How do I fix CVE-2025-32487?
To fix CVE-2025-32487, update Waymark to version 1.5.3 or later, which addresses the SSRF vulnerability.
Who is affected by CVE-2025-32487?
CVE-2025-32487 affects all versions of Waymark up to and including version 1.5.2.
What type of vulnerability is CVE-2025-32487?
CVE-2025-32487 is a Server-Side Request Forgery (SSRF) vulnerability.
Can CVE-2025-32487 lead to further attacks?
Yes, exploiting CVE-2025-32487 could potentially allow attackers to interact with internal services and escalate their access.
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/title
- agent/references
- agent/type
- agent/description
- agent/first-publish-date
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/softwarecombine
- agent/author
- agent/severity
- agent/event
- collector/nvd-api
- source/NVD
- agent/last-modified-date
- collector/epss-latest
- source/FIRST
- agent/source
- agent/tags
- agent/epss
- vendor/waymark
- canonical/waymark
- vendor/wordpress
- canonical/wordpress waymark