# CVE-2024-50490: WordPress PegaPoll plugin <= 1.0.2 - Arbitrary Option Update to Privilege Escalation vulnerability

> Attackers can update arbitrary options to escalate privileges due to missing authorization checks in the PegaPoll WordPress plugin.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Oct 2024
- **Updated:** 12 May 2026
- **Also known as:** GHSA-h3mr-3mvx-3w9g

## What is CVE-2024-50490?

CVE-2024-50490 is a critical missing authorization vulnerability in lowcage PegaPoll, published on 29 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing Authorization vulnerability in lowcage PegaPoll pegapoll allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects PegaPoll: from n/a through <= 1.0.2.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2024-50490 being exploited?

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

Public exploit code:

- PegaPoll <= 1.0.2 - Unauthenticated Arbitrary Options Update (github_poc): https://github.com/RandomRobbieBF/CVE-2024-50490

## Fix prompt for AI coding agents

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

What it is: CVE-2024-50490 is a critical missing authorization vulnerability in lowcage PegaPoll, published on 29 Oct 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-50490 in the wild and no public exploit code.

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

## Sources

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

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