dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2024-12612

HIGH · 7.5 CVSS v3.1 Published 2025-08-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 for Wordpress plugin for WordPress is vulnerable to SQL Injection via several parameters across multiple AJAX action in all versions up to, and including, 93.2.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 School Management System WordPress plugin versions up to 93.2.0 contains an unauthenticated SQL injection vulnerability affecting multiple AJAX action parameters. Attackers can inject malicious SQL queries due to insufficient user input escaping and lack of prepared SQL statements, enabling extraction of sensitive database information.

MitigationUpdate the School Management System plugin to the latest patched version immediately. If no patch exists, disable the plugin until a fix is available, or implement parameterized queries with proper escaping for all AJAX-handled SQL operations.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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. Confirm plugin installation and version
    Log into WordPress admin, navigate to Plugins > Installed Plugins, locate 'School Management System' and record the version number displayed. Alternatively, check the main plugin file (typically in wp-content/plugins/school-management or similar) for the 'Version' header in the plugin comment block.
    Affected if The installed version is 93.2.0 or lower.
  2. Compare version against affected range
    Take the recorded version number and compare it against the affected range. The vulnerability affects versions UP TO 93.2.0, meaning 93.2.0, 93.1.0, 93.0.0, and all earlier versions are vulnerable.
    Affected if The version is at or below 93.2.0.
  3. Verify unauthenticated AJAX accessibility
    Make an HTTP request to your site's /wp-admin/admin-ajax.php without logging in. Use a tool like curl: curl -s -o /dev/null -w '%{http_code}' https://yoursite.com/wp-admin/admin-ajax.php -d 'action=invalid_action'
    Affected if The server returns HTTP 200, indicating the AJAX endpoint is accessible without authentication.
  4. Identify plugin AJAX action handlers
    Inspect the plugin source code (PHP files in the plugin directory) for functions hooked to wp_ajax_ and wp_ajax_nopriv_ actions. Look for patterns like add_action('wp_ajax_...') or add_action('wp_ajax_nopriv_...') that handle user-supplied parameters.
    Affected if The plugin registers AJAX actions that handle user input without authentication (wp_ajax_nopriv_ hooks) and this plugin version is in the affected range.

You are affected if the School Management System plugin is installed with version 93.2.0 or lower and the site allows unauthenticated access to WordPress AJAX endpoints.

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 School Management System plugin to the latest patched version immediately. If no patch exists, disable the plugin until a fix is available, or implement parameterized queries with proper escaping for all AJAX-handled SQL operations.

Recommended fix Moderate confidence

Version 93.2.1 or later

  1. Navigate to your WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'School Management System for Wordpress' plugin
  4. If an update is available, click 'Update Now' to upgrade to the latest version (version 93.2.1 or later)
  5. Alternatively, download the latest version from CodeCanyon and upload it via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin version displays 93.2.1 or higher
Caveat Check plugin changelog for any breaking changes between your current version and the new version; minor version updates typically do not introduce breaking changes

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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