Location Weather <= 3.0.2 - Missing Authorization to Authenticated (Contributor+) Block Settings Modification and Cache Purging
Strategic Overview
- Status
- Patched in 3.0.3
- Affected Version
<= 3.0.2- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-7249
At a glance
CVE-2026-7249 is a medium-severity Missing Authorization vulnerability in the Location Weather WordPress plugin, affecting versions <= 3.0.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 3.0.3; sites on affected versions should update now. Disclosed May 2026, reported by momopon1415.
Vulnerability Overview
The Location Weather plugin for WordPress is vulnerable to unauthorized modification of data due to missing capability checks on the `splw_update_block_options()` and `lwp_clean_weather_transients()` functions in all versions up to, and including, 3.0.2. This makes it possible for authenticated attackers, with Contributor-level access and above, to disable all weather blocks and purge all weather cache transients. The nonce required for these actions is exposed to all authenticated users via `wp_localize_script()` on the `init` hook.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-862: Missing Authorization
Location Weather <= 3.0.2 carries this weakness at splw_update_block_options(), and reaching it takes an account at Contributor level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Location Weather the fix is 3.0.3: builds <= 3.0.2 are affected, anything from 3.0.3 onward is not.
Remediation
Update to version 3.0.3, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Location Weather 3.0.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Location Weather – WordPress Weather Forecast, Air Quality & Weather Widget
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C