WordPress MapSVG plugin <= 8.15.0 - Server Side Request Forgery (SSRF) vulnerability

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps MapSVG/MapSVG (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for MapSVG/MapSVG.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Aug 31, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Aug 31, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Aug 31, 2026

Sources and claim methodology

• Source referencepatchstack.com

Related CVEs

• Wallos: SSRF via Test Email Notification - unvalidated SMTP host/portAlso CWE-918
• Wallos: SSRF via OIDC Token/UserInfo URL ConfigurationAlso CWE-918
• Smarty: SSRF via redirect bypass of trusted_uri using {fetch}Also CWE-918
• Wallos incomplete fix for CVE-2026-33407: unauthenticated httpoxy SSRF still reachable via `endpoints/payments/search.php`Also CWE-918
• Wallos: SSRF via Unvalidated User-Level SMTP Host in Email Notification SettingsAlso CWE-918
• Wallos: Authenticated SSRF via per-user SMTP notification host (low-privilege user)Also CWE-918