CVE-2026-96815 WordPress Vitepos plugin <= 3.5.0 - Privilege Escalation vulnerability
High 7.2
Published
Updated
Check this codebase for CVE-2026-96815 and fix it if it is affected.
What it is: CVE-2026-96815 is a high-severity vulnerability in appsbd Vitepos, published on 30 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-96815 in the wild and no public exploit code.
Affected product: appsbd Vitepos. 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-2026-96815/ (Markdown: https://insights.sbomify.com/CVE-2026-96815/index.md)
Attackers can escalate privileges via custom role manipulation in the Vitepos WordPress plugin, requiring an upgrade to secure the site.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-96815?
CVE-2026-96815 is a high-severity vulnerability in appsbd Vitepos, published on 30 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Official description
Custom role Privilege Escalation in Vitepos <= 3.5.0 versions.
Weakness: CWE-266
Which versions are affected by CVE-2026-96815?
How do I fix CVE-2026-96815?
No fix has been published for CVE-2026-96815 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-96815 being exploited?
There is no known exploitation of CVE-2026-96815 in the wild and no public exploit code.
Sources
Also known as GHSA-x5hj-x887-f2r7.