dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-12155

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 SV100 Companion plugin for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to a missing capability check on the settings_import() function in all versions up to, and including, 2.0.02. This makes it possible for unauthenticated attackers 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. CVE-2024-54229 may be a duplicate of this issue.

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 SV100 Companion WordPress plugin has a broken access control vulnerability in the settings_import() function lacking a capability check, allowing unauthenticated attackers to modify arbitrary WordPress options. By enabling user registration and setting the default new user role to administrator, attackers can create administrative accounts and gain full site access. This is a critical privilege escalation vulnerability exploitable without authentication.

MitigationUpdate the SV100 Companion plugin to a patched version once released. As an interim measure, consider blocking unauthenticated access to the plugin's admin endpoints via WAF or access controls until the update is applied.

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

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. Verify SV100 Companion plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'SV100 Companion'. Alternatively, check the /wp-content/plugins/ directory for the sv100-companion folder.
    Affected if The SV100 Companion plugin is present and active on the WordPress site
  2. Check installed plugin version
    In WordPress admin, find SV100 Companion in Plugins list and note the version number displayed. Compare this against the version in which the vulnerability was patched once disclosed.
    Affected if Running an unpatched version of SV100 Companion that contains the vulnerability
  3. Confirm user registration is disabled
    Go to WordPress Settings > General and verify 'Membership: Anyone can register' is unchecked. Alternatively, inspect the 'users_can_register' option in the database or via WP-CLI: wp option get users_can_register
    Affected if User registration is enabled on the site (the 'users_can_register' option is set to 'true' or '1')
  4. Verify default new user role is not administrator
    Go to WordPress Settings > General and check 'Default New User Role'. It should NOT be set to 'Administrator'. Alternatively, check via WP-CLI: wp option get default_role
    Affected if The default_role option is set to 'administrator' (allows privilege escalation)
  5. Audit existing administrator accounts
    Go to WordPress Users and review all accounts with Administrator role. Check for unfamiliar or unexpected accounts, especially those created recently. Alternatively, query via WP-CLI: wp user list --role=administrator
    Affected if Unexpected or unknown administrator accounts exist, particularly ones created without your knowledge

The site is affected if SV100 Companion plugin is installed, user registration is enabled, default role is administrator, or unexpected admin accounts exist.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the SV100 Companion plugin to a patched version once released. As an interim measure, consider blocking unauthenticated access to the plugin's admin endpoints via WAF or access controls until the update is applied.

Recommended fix High confidence

SV100 Companion version 2.0.03 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the SV100 Companion plugin
  4. Click 'Update Now' if an update is available, or manually upload version 2.0.03 or later from wordpress.org/plugins/sv100-companion/
  5. Verify the update completed successfully
  6. Confirm the plugin is running version 2.0.03 or higher

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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