dbcve.org
Wp Job PortalWordPress extension · Wpjobportal

CVE-2023-52184

HIGH · 8.8 CVSS v3.1 Published 2024-01-05
Fix available
A fix is available. Upgrade to after 2.0.6 or later.
See remediation →
95/100
Remediation priority · Urgent
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 WP Job Portal WP Job Portal – A Complete Job Board.This issue affects WP Job Portal – A Complete Job Board: from n/a through 2.0.6.

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 · high confidence

Cross-Site Request Forgery (CSRF) vulnerability in the WP Job Portal WordPress plugin versions up to 2.0.6 allows attackers to trick authenticated users into performing unintended actions (like creating/modifying job listings or user data) by forging requests. The plugin lacks proper nonce verification on state-changing operations, enabling attackers to execute actions on behalf of legitimate users.

MitigationImplement anti-CSRF tokens (nonces) on all forms and AJAX endpoints in the plugin, and verify these nonces on every server-side state-changing operation. Additionally, consider adding SameSite cookie attributes and Same-Origin checks.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wp Job PortalWordPress extension
Affected:<= 2.0.6

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
High
Integrity
High
Availability
High

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

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. Check installed plugin version
    Go to WordPress admin dashboard > Plugins > Installed Plugins > Look for 'WP Job Portal' or 'Wpjobportal Wp Job Portal' and note the version displayed. Alternatively, check the plugin header in /wp-content/plugins/wp-job-portal/plugin.php for 'Version:' value.
    Affected if The version listed is 2.0.6 or lower.
  2. Identify state-changing forms in the plugin
    Navigate to the plugin admin panel and identify forms that modify data: job listing creation/editing forms, user profile forms, submission forms, or any form that changes data in the database.
    Affected if The plugin is actively used with forms that accept user input for job listings, resumes, or user data.
  3. Inspect form source code for nonce fields
    Right-click any state-changing form in the plugin (like job submission or user profile forms) and select 'View Page Source'. Search for 'wp_create_nonce', 'nonce', or '_wpnonce' input fields within the form tags.
    Affected if No nonce input field (wp_create_nonce, _wpnonce, or similar) is found inside the form HTML.
  4. Check AJAX endpoints for nonce verification
    Use browser developer tools > Network tab. Perform an action in the plugin (like submitting a job or saving a profile). Inspect the AJAX request headers or payload for a 'nonce' or '_wpnonce' parameter.
    Affected if AJAX requests that modify data do not include a nonce parameter in the request body or headers.
  5. Verify server-side nonce validation in plugin code
    If you have file access, examine the PHP handler files for state-changing actions (typically in /wp-content/plugins/wp-job-portal/ and look for functions handling form submissions or AJAX calls). Search for 'check_admin_referer' or 'wp_verify_nonce' calls before any database insert/update operations.
    Affected if Database modification operations (INSERT, UPDATE, DELETE) lack corresponding nonce verification calls nearby.

If the plugin version is 2.0.6 or lower AND any state-changing forms or AJAX endpoints are missing nonce fields or server-side verification, the environment is vulnerable to CVE-2023-52184.

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.

From vendor data
Upgrade available Upgrade to a release after 2.0.6
Interim mitigation

Implement anti-CSRF tokens (nonces) on all forms and AJAX endpoints in the plugin, and verify these nonces on every server-side state-changing operation. Additionally, consider adding SameSite cookie attributes and Same-Origin checks.

Fix this in Wp Job Portal Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-52184 — 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-52184 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