# CVE-2019-15111: Privilege escalation in n/a

> An attacker can escalate privileges in the wp-front-end-profile WordPress plugin, allowing unauthorized access to higher-level functions.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 21 Aug 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-878r-8pw6-2fjw

## What is CVE-2019-15111?

CVE-2019-15111 is a critical vulnerability in n/a, published on 21 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The wp-front-end-profile plugin before 0.2.2 for WordPress has a privilege escalation issue.

## Which versions are affected by CVE-2019-15111?

It affects 1 product.


Products: Wp Front End Profile Project Wp Front End Profile.

## How do I fix CVE-2019-15111?

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

## Is CVE-2019-15111 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-15110](https://insights.sbomify.com/CVE-2019-15110/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-15111 and fix it if it is affected.

What it is: CVE-2019-15111 is a critical vulnerability in n/a, published on 21 Aug 2019. 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-2019-15111 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-2019-15111/ (Markdown: https://insights.sbomify.com/CVE-2019-15111/index.md)
```

## Sources

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

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