Simple Job BoardWordPress extension · Presstigers
CVE-2024-1813
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 · uneditedThe Simple Job Board plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 2.11.0 via deserialization of untrusted input in the job_board_applicant_list_columns_value function. This makes it possible for unauthenticated attackers to inject a PHP Object. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code when a submitted job application is viewed.
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 confidenceThe Simple Job Board WordPress plugin has a PHP Object Injection vulnerability in the job_board_applicant_list_columns_value function. This function deserializes untrusted user-supplied input without proper validation, allowing unauthenticated attackers to inject arbitrary PHP objects. When a POP (property-oriented programming) chain exists via other plugins or themes on the target system, attackers can achieve remote code execution, file deletion, or data exfiltration by submitting or viewing a job application.
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
Simple Job BoardWordPress extension
< 2.11.1CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Simple Job Board plugin versionCheck the installed version of the Presstigers Simple Job Board plugin through WordPress admin plugins list or by inspecting the plugin header in the main plugin fileAffected if The installed version is lower than 2.11.1 (any version prior to 2.11.1 is affected)
-
Verify plugin is activeConfirm the Simple Job Board plugin is currently activated on the WordPress siteAffected if The plugin is active and the version is below 2.11.1 - inactive plugins with vulnerable versions are not exploitable in this context
-
Confirm job application functionality is enabledCheck if the job board has active job listings that accept applications. The vulnerability is triggered when submitting or viewing a job applicationAffected if Active job listings exist and the application submission feature is enabled - this is the attack vector for injecting malicious serialized data
-
Identify accessible applicant list viewsThe vulnerable function job_board_applicant_list_columns_value handles displaying applicant data in the admin panel. Determine if any user roles can access applicant listingsAffected if Any administrative or reviewer user role has access to view applicant lists, as this function deserializes input when rendering applicant columns
-
Audit for potential POP chain gadgetsReview installed plugins and themes for classes that could form a property-oriented programming chain. This is not a direct detection of this CVE but determines the full impact if exploitation succeedsAffected if Multiple or outdated plugins/themes are installed alongside Simple Job Board, increasing the likelihood that exploitable POP gadgets exist for RCE or file operations
A site is affected if Simple Job Board plugin version is below 2.11.1, the plugin is active, and job applications can be submitted or viewed by users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.11.1
Update the Simple Job Board plugin to version 2.11.1 or later. If no update is available, disable the plugin. Additionally, remove unused plugins and themes to reduce the likelihood of a viable POP chain being present.
Simple Job Board 2.11.1
- Backup your WordPress database and files before making any changes
- Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- Locate the Simple Job Board plugin and click 'Update now' when version 2.11.1 is available
- Alternatively, download Simple Job Board 2.11.1 from the WordPress Plugin Repository and upload it via Plugins > Add New > Upload Plugin
- Verify the update was successful by checking the plugin version in Plugins > Installed Plugins
- Test that job application submissions and listings still function correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Simple Job Board
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1813 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-1813 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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