CVE-2024-12607
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 · uneditedThe School Management System for Wordpress plugin for WordPress is vulnerable to SQL Injection via the 'id' parameter of the 'mj_smgt_show_event_task' AJAX action in all versions up to, and including, 92.0.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 authenticated attackers, with Custom-level access and above, 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 confidenceThe WordPress School Management System plugin (versions up to 92.0.0) contains a SQL injection vulnerability in the 'mj_smgt_show_event_task' AJAX action. The 'id' parameter is not properly escaped before being used in a SQL query, and the query lacks prepared statements, allowing authenticated attackers with Custom-level access or higher to inject arbitrary SQL commands to extract sensitive data.
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< 93.0.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify School Management System plugin is installedLocate the plugin in WordPress at wp-content/plugins/school-management-system/ or check via wp-admin > Plugins. Note the installed version from the plugin header.Affected if Plugin version is below 93.0.0 (versions up to and including 92.0.0 are affected)
-
Confirm the vulnerable AJAX action existsInspect plugin files for the function handling 'mj_smgt_show_event_task' AJAX action. Search plugin directory for the string 'mj_smgt_show_event_task' in PHP files.Affected if The AJAX action handler is present in the installed version
-
Check if the id parameter lacks sanitizationReview the code in the AJAX handler for the 'id' parameter. Look for absence of prepared statements, $wpdb->prepare(), or sanitization functions like intval() or sanitize_text_field() before using the 'id' in SQL queries.Affected if The 'id' parameter is used directly in SQL queries without $wpdb->prepare() or proper escaping
-
Identify if Custom-level users existIn WordPress admin, go to Users section and check for users with 'Custom' role (a custom role created by this plugin). Alternatively, query wp_usermeta for the wp_capabilities key containing 'custom'.Affected if Any user account with Custom-level access exists on the site
User is affected if the School Management System plugin version is below 93.0.0, the vulnerable AJAX action is enabled, and at least one user with Custom-level access exists or can be obtained by an attacker.
Generated from the published advisory. Verify against your own configuration.
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 · scoped93.0.0
Update the plugin to a version beyond 92.0.0 when available. If no patched version exists, implement proper input sanitization and convert the vulnerable SQL query to use prepared statements.
93.0.0
- Log in to WordPress admin dashboard
- Navigate to Dashboard > Updates or Plugins > Installed Plugins
- Locate the 'School Management System' plugin
- Click 'Update Now' to update to the latest version (93.0.0 or higher)
- Alternatively, go to Plugins > Add New > Upload and upload the version 93.0.0+ plugin package if auto-update is not available
- After updating, verify the plugin shows version 93.0.0 or later in the Plugins list
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12607 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-12607 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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