dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2024-12470

CRITICAL · 9.8 CVSS v3.1 Published 2025-01-07
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 School Management System – SakolaWP plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 1.0.8. This is due to the registration function not properly limiting what roles a user can register as. This makes it possible for unauthenticated attackers to register as an administrative user.

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 SakolaWP WordPress plugin has a privilege escalation vulnerability in its user registration function. The registration process does not properly validate or restrict the role that new users can assign to themselves, allowing unauthenticated attackers to register directly as administrators and gain full site control.

MitigationUpdate the SakolaWP plugin to version 1.0.9 or later. Until patched, disable user registration or implement Web Application Firewall rules to block suspicious registration requests, and audit existing user accounts for unauthorized admins.

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. Identify SakolaWP plugin installation and version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, locate SakolaWP, and note the version number displayed. Alternatively, check the plugin files in /wp-content/plugins/ for a version header in the main plugin PHP file.
    Affected if The plugin is installed and the version is below 1.0.9 (the fixed version)
  2. Confirm WordPress user registration is enabled
    Go to WordPress admin > Settings > General > Membership section and verify if 'Anyone can register' is checked. Also check if the 'New User Default Role' setting is set to a role other than 'Subscriber'.
    Affected if Anyone can register is enabled on the site
  3. Review registered user accounts for unauthorized administrators
    Navigate to WordPress admin > Users > All Users and examine the list for admin-level accounts that you did not create personally. Check the 'Registered' column date to identify recently created admin accounts.
    Affected if There are admin accounts that were not created by legitimate administrators, especially with recent registration dates
  4. Inspect plugin registration functionality configuration
    Check if the SakolaWP plugin has any frontend registration forms or endpoints (typically under /wp-json/ or custom registration routes). Look for any role selection parameters in registration requests.
    Affected if The plugin exposes a registration endpoint that accepts a role parameter without proper validation

You are affected if the SakolaWP plugin version is below 1.0.9 and user registration is enabled on the WordPress site, allowing potential unauthorized admin account creation.

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 SakolaWP plugin to version 1.0.9 or later. Until patched, disable user registration or implement Web Application Firewall rules to block suspicious registration requests, and audit existing user accounts for unauthorized admins.

Recommended fix Moderate confidence

Version 1.0.9 or later of the School Management System – SakolaWP plugin

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'School Management System – SakolaWP' plugin
  4. If an update is available, click 'Update Now' to update to the latest patched version
  5. After updating, verify the plugin version is 1.0.9 or higher
  6. Review any newly registered administrative users and remove any suspicious accounts created by unauthorized attackers
  7. Consider implementing additional access controls or monitoring for the registration functionality
Caveat Review plugin settings and custom configurations after upgrade as minor functionality changes may occur in point releases

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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