CVE-2024-12269

Safe Ai Malware Protection for WP <= 1.0.17 - Missing Authorization to Unauthenticated Database Export

2025-01-30 00:29
Tieu Pham Trong Nhan

Strategic Overview

Status
Patched in 1.0.18
Affected Version
<= 1.0.17
CVSS
7.5High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-12269
View all Safe Ai Malware Protection for WP vulnerabilities

At a glance

CVE-2024-12269 is a high-severity Missing Authorization vulnerability in the Safe Ai Malware Protection for WP WordPress plugin, affecting versions <= 1.0.17. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 1.0.18; sites on affected versions should update now. Disclosed January 2025, reported by Tieu Pham Trong Nhan.

Vulnerability Overview

The Safe Ai Malware Protection for WP plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the export_db() function in all versions up to, and including, 1.0.17. This makes it possible for unauthenticated attackers to retrieve a complete dump of the site's database.

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 privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-862: Missing Authorization

Safe Ai Malware Protection for WP <= 1.0.17 carries this weakness at export_db(), and reaching it takes no account at all. 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 Safe Ai Malware Protection for WP the fix is 1.0.18: builds <= 1.0.17 are affected, anything from 1.0.18 onward is not.

Remediation

Update to version 1.0.18, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Safe Ai Malware Protection for WP 1.0.18 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C