# CVE-2026-77016: Workeera Remote Tech Job Board < 1.0.6 - Subscriber+ Arbitrary File Deletion via Candidate Profile Mass Assignment


- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-wfmx-7744-w3xf

## What is CVE-2026-77016?

CVE-2026-77016 is a critical vulnerability in Unknown Workeera, published on 27 Aug 2026. 

### Official description

The Workeera  WordPress plugin before 1.0.6 does not restrict which values may be written to a user's own candidate profile, and does not validate or contain the stored file path before deleting it, allowing users with a role as low as subscriber to delete arbitrary files on the server.

Weakness: CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2026-77016?


## How do I fix CVE-2026-77016?

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

## Is CVE-2026-77016 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-77016 and fix it if it is affected.

What it is: CVE-2026-77016 is a critical vulnerability in Unknown Workeera, published on 27 Aug 2026. 
Exploitation: There is no known exploitation of CVE-2026-77016 in the wild and no public exploit code.

Affected product: Unknown Workeera. 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-77016/ (Markdown: https://insights.sbomify.com/CVE-2026-77016/index.md)
```

## Sources

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

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