dbcve.org
SuperioWordPress extension · Apusthemes

CVE-2024-12213

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-12
Fix available
A fix is available. Upgrade to after 1.2.76 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
The WP Job Board Pro plugin for WordPress is vulnerable to privilege escalation in all versions up to 2.3.16. This is due to the plugin allowing a user to supply the 'role' field when registering. This makes it possible for unauthenticated attackers to register as an administrator on vulnerable sites. Please note that this may have been patched sooner, however, the oldest available version for us to confirm this is patched in was 1.2.85.

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

The WP Job Board Pro WordPress plugin fails to validate or restrict the user-supplied 'role' parameter during registration. This allows unauthenticated attackers to specify 'administrator' as their role, granting them full administrative access to the WordPress site.

MitigationUpdate the plugin to version 2.3.17 or later (or at minimum version 1.2.85 if confirmed). If immediate patching is not possible, disable user registration functionality as a temporary workaround.

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
SuperioWordPress extension
Affected:<= 1.2.76

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
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 checks

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

  1. Check the installed version of the Superio theme
    Navigate to Appearance > Themes in the WordPress admin dashboard and locate the Superio theme. The version number is displayed on the theme thumbnail or in the theme details. Alternatively, open /wp-content/themes/superio/style.css and look for the 'Version:' header in the theme comment block.
    Affected if The installed version is 1.2.76 or lower.
  2. Verify if WordPress user registration is enabled
    Go to Settings > General in the WordPress admin dashboard and check the box labeled 'Membership: Anyone can register'. If this is checked, user registration is enabled.
    Affected if User registration is enabled on the site.
  3. Inspect the registration form for role parameter handling
    Navigate to the WP Job Board Pro settings or Superio theme options where registration forms are configured. Look for any field that accepts or allows selection of a user role, particularly one that might accept 'administrator' as a value.
    Affected if The registration form allows users to specify or influence their role without server-side validation.
  4. Review all administrator-level user accounts
    Go to Users > All Users in the WordPress admin dashboard. Examine the list of users with the Administrator role. Look for unfamiliar accounts, accounts with email addresses you do not recognize, or accounts created recently that you did not create.
    Affected if There are administrator accounts that you did not create or do not recognize.

You are affected if the Superio theme version is 1.2.76 or lower AND user registration is enabled on your WordPress site.

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
Upgrade available Upgrade to a release after 1.2.76
Interim mitigation

Update the plugin to version 2.3.17 or later (or at minimum version 1.2.85 if confirmed). If immediate patching is not possible, disable user registration functionality as a temporary workaround.

Recommended fix High confidence

Superio theme version 1.2.85 or later

  1. Backup your WordPress site before making any changes
  2. Download Superio theme version 1.2.85 or later from ThemeForest
  3. Navigate to Appearance > Themes in WordPress admin
  4. Deactivate and delete the current Superio theme (or use the WordPress theme uploader to upload the new version)
  5. Install and activate the updated Superio theme version 1.2.85 or later
  6. Verify the update was successful by checking the theme version in Appearance > Themes
  7. Consider testing user registration functionality to confirm the privilege escalation vulnerability is resolved

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

Fix this in Superio Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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