# CVE-2017-6577: SQL injection in n/a

> An attacker with WordPress admin access can exploit SQL injection in the Mail Masta plugin to read or modify database contents.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rjfv-jxfw-m89c

## What is CVE-2017-6577?

CVE-2017-6577 is a high-severity SQL injection vulnerability in n/a, published on 9 Mar 2017. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A SQL injection issue is exploitable, with WordPress admin access, in the Mail Masta (aka mail-masta) plugin 1.0 for WordPress. This affects ./inc/subscriber_list.php with the POST Parameter: list_id.

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

## Which versions are affected by CVE-2017-6577?

It affects 1 product.


Products: Mail-Masta Project Mail-Masta.

## How do I fix CVE-2017-6577?

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

## Is CVE-2017-6577 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-6095](https://insights.sbomify.com/CVE-2017-6095/): SQL injection in n/a (critical 9.8)
- [CVE-2016-10956](https://insights.sbomify.com/CVE-2016-10956/): Path traversal in n/a (high 7.5)
- [CVE-2017-6570](https://insights.sbomify.com/CVE-2017-6570/): SQL injection in n/a (high 7.2)
- [CVE-2017-6571](https://insights.sbomify.com/CVE-2017-6571/): SQL injection in n/a (high 7.2)
- [CVE-2017-6572](https://insights.sbomify.com/CVE-2017-6572/): SQL injection in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6577 and fix it if it is affected.

What it is: CVE-2017-6577 is a high-severity SQL injection vulnerability in n/a, published on 9 Mar 2017. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-6577 in the wild and no public exploit code.

Affected product: n/a. 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-2017-6577/ (Markdown: https://insights.sbomify.com/CVE-2017-6577/index.md)
```

## Sources

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

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