CVE-2024-9658
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 privilege escalation via account takeover in all versions up to, and including, 93.0.0. This is due to the plugin not properly validating a user's identity prior to updating their details like email and password through the mj_smgt_update_user() and mj_smgt_add_admission() functions, along with a local file inclusion vulnerability. This makes it possible for authenticated attackers, with student-level access and above, to change arbitrary user's email addresses and passwords, including administrators, and leverage that to gain access to their account. This was escalated four months ago after no response to our initial outreach, yet it still vulnerable.
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 School Management System WordPress plugin versions up to 93.0.0 fail to validate user identity before allowing updates to email and password fields via the mj_smgt_update_user() and mj_smgt_add_admission() functions. This allows authenticated attackers with student-level access to modify arbitrary user credentials, including administrators, leading to full account takeover. A local file inclusion vulnerability is also present.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if School Management System plugin is installedCheck your WordPress plugins directory or use wp plugin list to enumerate installed pluginsAffected if The Dasinfomedia School Management System plugin appears in the installed plugins list
-
Check installed plugin versionView the plugin main file header or use wp plugin get school-management-system to retrieve the version numberAffected if The installed version is 93.0.0 or lower (any version <= 93.0.0)
-
Locate vulnerable function mj_smgt_update_userSearch the plugin source code for the function mj_smgt_update_user() and inspect its implementation for missing user capability checksAffected if The function exists and lacks current_user_can() or similar authorization validation before processing user updates
-
Locate vulnerable function mj_smgt_add_admissionSearch the plugin source code for the function mj_smgt_add_admission() and review its access control logicAffected if The function exists and does not validate user identity before allowing email or password modifications
-
Verify student role exists and can access update endpointsCheck WordPress user roles capability table and test whether the student role has permissions to access user update functionsAffected if Student role users can access endpoints that modify administrator account credentials
-
Confirm local file inclusion componentReview the plugin for file inclusion functions (include, require, file_get_contents) that use unsanitized user inputAffected if The plugin contains file inclusion vulnerabilities that could be chained with the authorization flaw
Your environment is affected if the School Management System plugin version is 93.0.0 or lower and the vulnerable functions mj_smgt_update_user() and mj_smgt_add_admission() lack proper authorization checks.
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 · scopedImplement proper authorization checks ensuring users can only modify their own account details, add current-password verification before allowing email/password changes, and remediate the local file inclusion vector.
Version > 93.0.0 (check for latest available version)
- Check if a newer version of the School Management System plugin (version > 93.0.0) is available in the WordPress plugin repository or your CodeCanyon account
- If a newer version is available, update the plugin to the latest version
- If no newer version is available, consider temporarily disabling the plugin until a security update is released
- Alternatively, contact the plugin developer directly to request a security patch for this vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9658 — 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-9658 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