dbcve.org
SuperioWordPress extension · Apusthemes

CVE-2024-12296

HIGH · 8.8 CVSS v3.1 Published 2025-02-12
Fix available
A fix is available. Upgrade to after 2.3 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Apus Framework plugin for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to a missing capability check on the 'import_page_options' function in all versions up to, and including, 2.4. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update arbitrary options on the WordPress site. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site. NOTE: This vulnerability was partially fixed in version 2.4.

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 Apus Framework WordPress plugin lacks a capability check on the import_page_options function, allowing any authenticated user with Subscriber-level access or higher to modify arbitrary WordPress options. Attackers can enable user registration and change the default role to Administrator, then register an account with full admin privileges.

MitigationUpdate to the latest version of Apus Framework (after 2.4) and audit existing user accounts for unauthorized administrators. Consider implementing WAF rules to block unauthorized option modifications until the patch is applied.

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:<= 2.3

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify if Apus Framework Superio is installed
    Check your WordPress plugins or theme directory for the Apusthemes Superio theme/plugin and note its installed version number
    Affected if The installed version is 2.3 or lower (the vulnerable versions)
  2. Verify if user registration is enabled
    In WordPress admin, go to Settings > General and check 'Membership: Anyone can register' - also check the wp_options table for 'users_can_register' value and who modified it
    Affected if User registration is enabled and was not intentionally enabled by an administrator
  3. Audit user accounts for unauthorized Administrators
    Navigate to Users > All Users in WordPress admin and review all accounts with Administrator role, especially accounts you do not recognize or that were created recently
    Affected if There are Administrator accounts you did not create or that were created after the plugin was installed
  4. Check for suspicious new user registrations
    Review user registration dates in the wp_users table and correlate with plugin installation date or known admin activity
    Affected if New user accounts with Administrator role exist beyond the original admin account

You are affected if the Superio theme/plugin version is 2.3 or lower AND you find unauthorized Administrator accounts or unexpectedly enabled user registration that you did not configure.

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 2.3
Interim mitigation

Update to the latest version of Apus Framework (after 2.4) and audit existing user accounts for unauthorized administrators. Consider implementing WAF rules to block unauthorized option modifications until the patch is applied.

Recommended fix High confidence

Apus Framework version 2.4 or later (or Superio theme version with patched Apus Framework)

  1. 1. Backup your WordPress database and files before making any changes.
  2. 2. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins.
  3. 3. Locate the Apus Framework plugin (or Superio theme if the framework is bundled).
  4. 4. Check the current version number to confirm it is 2.4 or below.
  5. 5. Update the Apus Framework plugin to version 2.4 or later, or update the Superio theme to a version that includes the patched Apus Framework.
  6. 6. After updating, verify the 'import_page_options' function no longer allows unauthorized access by testing with a Subscriber-level account.
  7. 7. If the vulnerability persists after updating to 2.4, consider additional hardening measures such as limiting user registration settings and monitoring for unauthorized administrative accounts.
Caveat Minimal risk; standard plugin/theme update. Ensure compatibility with your WordPress version before upgrading.

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
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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