# CVE-2024-3076: MM-email2image <= 0.2.5 - Stored XSS via CSRF

> Attackers can inject stored XSS payloads via CSRF, allowing admin account takeover in the MM-email2image WordPress plugin.

- **Severity:** Low 3.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Apr 2024
- **Updated:** 20 Nov 2024
- **Also known as:** GHSA-h2vp-92vw-43mf

## What is CVE-2024-3076?

CVE-2024-3076 is a low-severity cross-site scripting vulnerability in Unknown MM-email2image, published on 26 Apr 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The MM-email2image WordPress plugin through 0.2.5 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Mmilan81 Mm-Email2image.

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

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

## Is CVE-2024-3076 being exploited?

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

## Other vulnerabilities in Unknown MM-email2image

- [CVE-2024-3075](https://insights.sbomify.com/CVE-2024-3075/): MM-email2image <= 0.2.5 - Contributor+ Stored XSS (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-3076 is a low-severity cross-site scripting vulnerability in Unknown MM-email2image, published on 26 Apr 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-3076 in the wild and no public exploit code.

Affected product: Unknown MM-email2image. 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-3076/ (Markdown: https://insights.sbomify.com/CVE-2024-3076/index.md)
```

## Sources

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

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