WordPress security changelog
HIGH CVE-2023-1509 Modified

GMAce: Code execution

GMAce is affected by code execution. The vulnerable path is reachable without authentication. Successful exploitation can run attacker-controlled code in the WordPress hosting account.

CVE / CNA score 8.8 CVSS 3.1 · security@wordfence.com
NVD score 8.8 CVSS 3.1 · nvd@nist.gov
Component
GMAce
Plugin slug
gmace
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Mar 29, 2023
Weakness
CWE-352 — Cross-Site Request Forgery (CSRF)

This CVE was published Mar 29, 2023 and is one of 3 known issues for this plugin.

What to do

Update, patch or deactivate.

Update GMAce 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.

Source record

Technical description

The GMAce plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.5.2. This is due to missing nonce validation on the gmace_manager_server function called via the wp_ajax_gmace_manager AJAX action. This makes it possible for unauthenticated attackers to modify arbitrary files and achieve remote code execution via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

NVD vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

References

Primary and upstream sources