# CVE-2024-7950: Missing authorization in WP Job Portal – AI-Powered Recruitment System for Company or Job Board website

> Unauthenticated attackers can execute arbitrary code, update settings, and create administrator accounts in WP Job Portal due to missing authorization checks.

- **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:** 4 Sep 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-pf98-xx8j-74qh

## What is CVE-2024-7950?

CVE-2024-7950 is a critical missing authorization vulnerability in wpjobportal WP Job Portal – AI-Powered Recruitment System for Company or Job Board website, published on 4 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Job Portal – A Complete Recruitment System for Company or Job Board website plugin for WordPress is vulnerable to Local File Inclusion, Arbitrary Settings Update, and User Creation in all versions up to, and including, 2.1.6 via several functions called by the 'checkFormRequest' function. This makes it possible for unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included. Attackers can also update arbitrary settings and create user accounts even when registration is disabled, leading to user creation with a default role of Administrator.

Weakness: CWE-862 (Missing Authorization), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Wpjobportal Wp Job Portal.

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

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

## Is CVE-2024-7950 being exploited?

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

## Other vulnerabilities in wpjobportal WP Job Portal – AI-Powered Recruitment System for Company or Job Board website

- [CVE-2023-4490](https://insights.sbomify.com/CVE-2023-4490/): WP Job Portal < 2.0.6 - Unauthenticated SQLi (critical 9.8)
- [CVE-2025-48274](https://insights.sbomify.com/CVE-2025-48274/): WordPress WP Job Portal plugin <= 2.3.2 - SQL Injection Vulnerability (critical 9.3)
- [CVE-2025-47438](https://insights.sbomify.com/CVE-2025-47438/): WordPress WP Job Portal plugin <= 2.3.1 - Local File Inclusion vulnerability (high 8.1)
- [CVE-2025-48273](https://insights.sbomify.com/CVE-2025-48273/): WordPress WP Job Portal plugin <= 2.3.2 - Arbitrary File Download Vulnerability (high 7.5)
- [CVE-2025-26935](https://insights.sbomify.com/CVE-2025-26935/): WordPress WP Job Portal plugin <= 2.2.8 - Local File Inclusion vulnerability (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-7950 is a critical missing authorization vulnerability in wpjobportal WP Job Portal – AI-Powered Recruitment System for Company or Job Board website, published on 4 Sep 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-7950 in the wild and no public exploit code.

Affected product: wpjobportal WP Job Portal – AI-Powered Recruitment System for Company or Job Board website. 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-7950/ (Markdown: https://insights.sbomify.com/CVE-2024-7950/index.md)
```

## Sources

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

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