Safeguard
Vulnerability Analysis•

CVE-2023-23715: Medium Missing Authorization in JobBoardWP Plugin

JobBoardWP through 1.2.2 has an IDOR that can remove other people's job listings. Medium severity, CVSS 5.2. Update to JobBoardWP 1.2.3 or later.

Safeguard Security Team
3 min read

CVE-2023-23715 is a medium severity missing authorization flaw (CVSS 5.2) in the JobBoardWP WordPress plugin, affecting every version through 1.2.2. Update to 1.2.3 or later. Check every site you run, because plugin copies on forgotten staging sites are easy to miss.

What's affected

  • JobBoardWP plugin, all versions up to and including 1.2.2, per the record and the Patchstack listing.
  • Fixed version: 1.2.3, per Patchstack.
  • The record shows high privileges and user interaction are needed.
  • Severity: CVSS 3.1 score 5.2 Medium, vector CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:H.

How to check if you're exposed

If you manage the site with WP-CLI, list the plugin and its version:

wp plugin list --fields=name,version,status | grep -i jobboardwp

The plugin directory slug is jobboardwp. Without WP-CLI, open Plugins, Installed Plugins in the WordPress admin and read the version under the JobBoardWP entry. Check every site you run, including staging copies and sites that sit behind a hosting dashboard you rarely open. Multisite networks should also check each subsite, because a plugin can be active on one and absent on another.

What to do now

  1. Find every WordPress site that has JobBoardWP installed, including staging copies, and read the version.
  2. Update the plugin to 1.2.3 or later and confirm the version in the plugin list.
  3. If you cannot update right away, deactivate the plugin until you can.
  4. Review web server logs for unexpected requests to the plugin around the time you learned of the issue.

Why it matters

The weakness is missing authorization (CWE-862 (Missing Authorization)). Broken access control means a function runs without checking that the caller is allowed to use it. WordPress plugins register many actions that requests can reach, so each one needs an explicit capability check. When the check is missing, the plugin trusts the request, whatever role the requester holds.

Patchstack describes this one as an insecure direct object reference that leads to job removal. In an IDOR, the plugin accepts an identifier from the request and acts on the matching object without checking that the requester owns it. Changing the identifier then reaches other people's records. The record shows high privileges and user interaction are required, which keeps the score at 5.2. CISA has not listed this CVE in its Known Exploited Vulnerabilities catalog, according to the record we hold, and none of the pages we read said it is being exploited.

Auto updates for plugins are worth enabling for low risk plugins that you do not customize. They shrink the window between a fix and your site running it. Keep a staging copy for plugins that touch checkout, forms or user accounts, so you can test before you update production.

Quick check

What does IDOR mean?

Insecure direct object reference. The code uses an ID from the request to find an object, and never checks that the requester may touch that object.

What is the impact?

Per the vector and the Patchstack title, job listings could be removed, which affects integrity and availability of content.

Sources

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.