CVE-2023-47188
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 · uneditedMissing Authorization vulnerability in PressTigers Simple Job Board simple-job-board allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Simple Job Board: from n/a through <= 2.10.5.
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 confidenceA missing authorization vulnerability exists in the PressTigers Simple Job Board WordPress plugin (versions up to 2.10.5) that allows attackers to exploit incorrectly configured access control security levels. This critical flaw enables unauthorized users to access functionality or data that should be restricted to privileged users due to improper or missing permission checks in the plugin's code.
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< 2.10.6CVSS 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.
-
Verify Simple Job Board plugin is installedCheck if the plugin directory exists at wp-content/plugins/simple-job-board/ or look for 'Simple Job Board' in WordPress plugin list via WP Admin > PluginsAffected if The plugin is installed and active
-
Check installed plugin versionOpen the main plugin file (usually simple-job-board.php) and locate the 'Version:' header in the plugin comment block, or check readme.txt for the version numberAffected if Version is below 2.10.6 (e.g., 2.10.5 or earlier)
-
Identify accessible endpoints without authorizationTest unauthenticated or low-privilege user access to plugin AJAX actions, admin pages, or front-end submission endpoints by examining network requests or reviewing the plugin's PHP files for 'add_action' calls that lack capability checks (e.g., missing 'manage_options' or 'edit_posts' verification)Affected if Sensitive plugin functions (like job posting, applicant management, or settings modifications) are reachable without proper permission verification
-
Verify role-based access control is enforcedReview plugin PHP code for current_user_can() or capability checks before executing sensitive functions in files within /includes/ or /admin/ directoriesAffected if No capability checks exist before sensitive operations, or checks are present but easily bypassed
You are affected if Simple Job Board version below 2.10.6 is installed and sensitive plugin functionality lacks proper authorization checks, allowing lower-privilege users to access restricted actions.
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.10.6
Upgrade to the latest version of Simple Job Board if available, or implement proper authorization checks on all sensitive functionality and data access points within the plugin to enforce role-based access controls.
2.10.6
- 1. Backup your WordPress site and database before proceeding with any updates.
- 2. Navigate to the WordPress admin dashboard > Plugins section.
- 3. Locate the Simple Job Board plugin in your installed plugins list.
- 4. Check if an update to version 2.10.6 or later is available.
- 5. If an update is available, click 'Update Now' to upgrade to version 2.10.6.
- 6. If automatic updates are not available, manually download version 2.10.6 from the WordPress Plugin Repository or the vendor, then upload and replace the existing plugin files.
- 7. After updating, verify that the plugin functions correctly by testing job board features.
- 8. Confirm the updated version number in the Plugins section of WordPress admin.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47188 — 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-2023-47188 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