← WordPress Vulnerabilities
WordPress security by component

Location Weather

Location Weather is a WordPress component with 3 published CVE records in this archive. The latest tracked vulnerability was published Jul 27, 2026; the highest CVE/CNA score is 6.5.

Plugin slug: location-weather

CVE-2026-66433: Location Weather contributor input permits cross-site scripting

Location Weather through 3.0.6 lets a Contributor supply attacker-controlled input that reaches a browser-executable output context without adequate neutralization. The payload can execute in the site's origin when another user views the crafted output. The Patchstack CNA record does not disclose whether the payload is reflected or stored, or identify the endpoint, field, parameter or rendering function.

PublishedJul 27, 2026
Known safe version3.0.7
Safe version
Jul 27, 2026 CVE-2026-66433
Location Weather contributor input permits cross-site scripting
Location Weather through 3.0.6 lets a Contributor supply attacker-controlled input that reaches a browser-executable output context without adequate neutralization. The payload can execute in the site's origin when another user views the crafted output. The Patchstack CNA record does not disclose whether the payload is reflected or stored, or identify the endpoint, field, parameter or rendering function.
3.0.7
CVE6.5
NVDPending
May 22, 2026 CVE-2026-7249
Location Weather – WordPress Weather Forecast, AQI, Temperature and Weather Widget: A security weakness
Location Weather – WordPress Weather Forecast, AQI, Temperature and Weather Widget is affected by a security weakness. Exploitation requires at least contributor-level access. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is <= 3.0.2.
> 3.0.2
CVE4.3
NVDPending
Feb 13, 2023 CVE-2023-0360
Location Weather: Cross-site scripting
Location Weather is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE5.4
NVD5.4