# CVE-2024-34822: WordPress weMail plugin <= 1.14.2 - Broken Access Control vulnerability

> An attacker can bypass authorization checks in the weMail WordPress plugin to access restricted functionality without proper permissions.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jun 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-hg9h-v98r-f5mq

## What is CVE-2024-34822?

CVE-2024-34822 is a medium-severity missing authorization vulnerability in weDevs weMail, published on 11 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing Authorization vulnerability in weDevs weMail.This issue affects weMail: from n/a through 1.14.2.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Wedevs Wemail.

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

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

## Is CVE-2024-34822 being exploited?

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

## Other vulnerabilities in weDevs weMail

- [CVE-2024-43238](https://insights.sbomify.com/CVE-2024-43238/): WordPress weMail plugin <= 1.14.5 - Cross Site Scripting (XSS) vulnerability (high 7.1)
- [CVE-2025-47540](https://insights.sbomify.com/CVE-2025-47540/): WordPress weMail plugin <= 1.14.13 - Sensitive Data Exposure Vulnerability (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-34822 is a medium-severity missing authorization vulnerability in weDevs weMail, published on 11 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-34822 in the wild and no public exploit code.

Affected product: weDevs weMail. 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-34822/ (Markdown: https://insights.sbomify.com/CVE-2024-34822/index.md)
```

## Sources

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

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