# CVE-2024-53807: WordPress WP Mailster plugin <= 1.8.16.0 - SQL Injection vulnerability

> An attacker can perform blind SQL injection to read sensitive database information from the WP Mailster WordPress plugin.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Dec 2024
- **Updated:** 12 May 2026
- **Also known as:** GHSA-3xg5-7p4x-v3wx

## What is CVE-2024-53807?

CVE-2024-53807 is a high-severity SQL injection vulnerability in brandtoss WP Mailster, published on 6 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in brandtoss WP Mailster wp-mailster allows Blind SQL Injection.This issue affects WP Mailster: from n/a through <= 1.8.16.0.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2024-53807?

It affects 1 product.


Products: Wpmailster Wp Mailster.

## How do I fix CVE-2024-53807?

No fix has been published for CVE-2024-53807 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-53807 being exploited?

There is no known exploitation of CVE-2024-53807 in the wild and no public exploit code.

## Other vulnerabilities in brandtoss WP Mailster

- [CVE-2024-53804](https://insights.sbomify.com/CVE-2024-53804/): WordPress WP Mailster plugin <= 1.8.16.0 - Sensitive Data Exposure vulnerability (high 7.5)
- [CVE-2024-53805](https://insights.sbomify.com/CVE-2024-53805/): WordPress WP Mailster plugin <= 1.8.16.0 - Broken Access Control vulnerability (high 7.5)
- [CVE-2025-24598](https://insights.sbomify.com/CVE-2025-24598/): WordPress WP Mailster plugin <= 1.8.17.0 - Reflected Cross Site Scripting (XSS) vulnerability (high 7.1)
- [CVE-2025-24559](https://insights.sbomify.com/CVE-2025-24559/): WordPress WP Mailster plugin <= 1.8.15.0 - Reflected Cross Site Scripting (XSS) vulnerability (high 7.1)
- [CVE-2024-53803](https://insights.sbomify.com/CVE-2024-53803/): WordPress WP Mailster plugin <= 1.8.16.0 - Broken Access Control vulnerability (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-53807 and fix it if it is affected.

What it is: CVE-2024-53807 is a high-severity SQL injection vulnerability in brandtoss WP Mailster, published on 6 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-53807 in the wild and no public exploit code.

Affected product: brandtoss WP Mailster. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-53807/ (Markdown: https://insights.sbomify.com/CVE-2024-53807/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-53807
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-53807
- OSV: https://osv.dev/vulnerability/CVE-2024-53807

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-53807/
Summaries are generated and may contain mistakes; the official description above is the record.