Wpml: A security weakness
Wpml is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
- Component
- Wpml
- Plugin slug
wpml- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Mar 30, 2015
This CVE was published Mar 30, 2015 and is one of 7 known issues for this plugin.
Update, patch or deactivate.
Update Wpml to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The WPML plugin before 3.1.9 for WordPress does not properly handle multiple actions in a request, which allows remote attackers to bypass nonce checks and perform arbitrary actions via a request containing an action POST parameter, an action GET parameter, and a valid nonce for the action GET parameter.
NVD vector: AV:N/AC:L/Au:N/C:P/I:P/A:P