dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2023-52212

MEDIUM · 5.4 CVSS v3.1 Published 2026-01-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-Site Request Forgery (CSRF) vulnerability in Automattic WP Job Manager allows Cross Site Request Forgery.This issue affects WP Job Manager: from n/a through 2.0.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the WP Job Manager plugin allows attackers to induce authenticated users to perform unintended actions (such as modifying job listings or settings) by tricking them into submitting malicious requests.

MitigationImplement anti-CSRF tokens (nonce validation) on all state-changing forms and AJAX actions within the plugin, and ensure SameSite cookie attributes are properly configured.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm WP Job Manager plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Job Manager', or check the /wp-content/plugins/wp-job-manager directory exists on the server
    Affected if The plugin is not installed on the WordPress site
  2. Identify installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and click on WP Job Manager to view the version number, or inspect the plugin's main PHP file header for 'Version:' tag
    Affected if The version cannot be determined or is not listed
  3. Compare installed version against affected range
    Cross-reference your installed version with the official CVE advisory or plugin changelog to determine if it falls within vulnerable versions
    Affected if The installed version is within the affected version range for CVE-2023-52212
  4. Check for state-changing admin actions
    Identify if the site uses job submission, job management, or plugin settings forms accessible to authenticated users (check for endpoints like /wp-admin/admin.php?page=job-manager-setup, job submission pages, or user dashboard features)
    Affected if The site has authenticated user roles with ability to submit or modify job listings or settings
  5. Verify nonce validation presence in forms
    Examine the plugin's PHP source code for form handlers and AJAX actions, specifically looking for wp_verify_nonce() or check_admin_referer() calls in functions that process job submissions or settings changes
    Affected if State-changing forms and AJAX actions lack nonce verification (vulnerable to CSRF)

A WordPress site is affected if it runs WP Job Manager with an installed version within the CVE-affected range and has authenticated user access to job management features without proper nonce protection on forms.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (nonce validation) on all state-changing forms and AJAX actions within the plugin, and ensure SameSite cookie attributes are properly configured.

Recommended fix Moderate confidence

WP Job Manager 2.0.1 or later

  1. 1. Identify the current installed version of WP Job Manager plugin
  2. 2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. 3. Locate WP Job Manager and note the current version number
  4. 4. Check if the current version is 2.0.0 or earlier
  5. 5. Before upgrading, backup the WordPress database and files
  6. 6. Navigate to Plugins > Add New > Upload to upload the latest version
  7. 7. Alternatively, update directly via Dashboard > Updates or from the Plugins page
  8. 8. Verify the update completed successfully
Caveat Review changelog for any template changes or deprecated functions that may affect custom themes or extensions

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-52212 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-52212 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data