# CVE-2025-6042: Privilege escalation in Lisfinity Core - Lisfinity Core plugin used for pebas® Lisfinity WordPress theme

> Unauthenticated attackers can escalate privileges to Editor via unrestricted API access in the Lisfinity Core WordPress plugin.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-3386-wpw4-2hcp

## What is CVE-2025-6042?

CVE-2025-6042 is a high-severity vulnerability in Lisfinity Core - Lisfinity Core plugin used for pebas® Lisfinity WordPress theme, published on 15 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Lisfinity Core - Lisfinity Core plugin used for pebas® Lisfinity WordPress theme plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 1.4.0. This is due to the plugin assigning the editor role by default. While limitations with respect to capabilities are put in place, use of the API is not restricted. This vulnerability can be leveraged together with CVE-2025-6038 to obtain admin privileges.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2025-6042?


## How do I fix CVE-2025-6042?

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

## Is CVE-2025-6042 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-6042 and fix it if it is affected.

What it is: CVE-2025-6042 is a high-severity vulnerability in Lisfinity Core - Lisfinity Core plugin used for pebas® Lisfinity WordPress theme, published on 15 Oct 2025. 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-2025-6042 in the wild and no public exploit code.

Affected product: Lisfinity Core - Lisfinity Core plugin used for pebas® Lisfinity WordPress theme. 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-2025-6042/ (Markdown: https://insights.sbomify.com/CVE-2025-6042/index.md)
```

## Sources

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

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