Safeguard
Vulnerability Analysis•

CVE-2022-41786: Medium Access Flaw in WP Job Portal Plugin

CVE-2022-41786 is a medium (5.4) missing authorization bug in the WP Job Portal WordPress plugin up to version 2.0.1. Update to 2.0.2 or later.

Safeguard Security Team
3 min read

CVE-2022-41786 is a medium severity (CVSS 5.4) missing authorization flaw in the WP Job Portal plugin for WordPress, versions up to and including 2.0.1. Update to 2.0.2 or later. Check your installed version and apply the update through your normal change process.

What's affected

The record lists WP Job Portal from WP Job Portal, from the first release through 2.0.1. Patchstack gives the patched version as 2.0.2. Patchstack gives the required privilege as none, so it is unauthenticated.

The record scores it 5.4 (Medium) with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L. Patchstack labels its own priority Low. The weakness class is CWE-862 (Missing Authorization).

How to check if you're exposed

Start with an inventory. If you manage the site with WP-CLI, this lists every plugin with its version and whether an update is waiting:

wp plugin list --fields=name,status,version,update

Look for the folder wp-job-portal. That folder name comes from the Patchstack entry for this issue, so confirm it matches what sits under wp-content on your site. Without WP-CLI, open the Plugins screen in the dashboard and read the version shown under the name. Version 2.0.1 or lower is affected. Version 2.0.2 or later is patched.

Check staging copies, old multisite subsites and inactive plugins too. A deactivated plugin is still on disk, and some of these bugs are reachable through files that load even when the plugin is switched off, so deactivation alone is not a fix. Delete what you do not use.

What to do now

  1. Update WP Job Portal to 2.0.2 or a newer release.
  2. Review the site's user list and remove accounts you do not recognise.
  3. Turn on automatic updates for the plugin so the next fix lands without a ticket.

Why it matters

A job board lets the public browse and apply, so many of its routes have to be reachable without an account. That makes authorization checks easy to forget on the routes that should be restricted. The record describes this flaw only as missing authorization, and Patchstack's URL labels it unauthorized actions.

The vector in the record includes user interaction, which means a victim, such as a logged in administrator, has to do something for the attack to work. Combined with low integrity and availability impact, the score sits at medium. Patchstack rates its own priority Low.

I did not find a description of the specific action, so this post does not name one. Patch to 2.0.2 or later and read the plugin's changelog for context. The record's KEV flag is false, and nothing I fetched reports exploitation in the wild.

Quick check

The Patchstack page URL mentions version 1.1.9. Which version is right?

The record and the Patchstack page body both say versions up to 2.0.1 are affected and 2.0.2 is patched. The URL text appears to be an older label. Trust the version table.

Does this need a login?

Patchstack lists the required privilege as unauthenticated, though the record's vector notes user interaction is required.

Sources

Safeguard can help you see this across many sites or repositories at once. Paste a manifest into the free in-browser dependency scan at gold.safeguard.sh/scan or look the issue up in the Gold directory to see how the record is tracked.

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.