CVE-2024-9659
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 arbitrary file uploads due to missing file type validation in the mj_smgt_user_avatar_image_upload() function in all versions up to, and including, 91.5.0. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.
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 has an arbitrary file upload vulnerability in the mj_smgt_user_avatar_image_upload() function due to missing file type validation. Unauthenticated attackers can upload arbitrary files, potentially including PHP shells, leading to remote code execution.
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< 92.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check if School Management System plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'School Management System' or 'Dasinfomedia School Management System'. Note the installed version from the plugin version column.Affected if The plugin is installed and the version is below 92.0.0 (e.g., 91.x.x or earlier)
-
Verify plugin version via file inspectionAccess the plugin directory via FTP or file manager (wp-content/plugins/school-management-system/) and open the main plugin file (e.g., school-mgmt.php) to read the Version header in the plugin comment block.Affected if The Version field shows a number lower than 92.0.0
-
Confirm the vulnerable upload function existsSearch the plugin files for the function 'mj_smgt_user_avatar_image_upload' in the includes or admin folders, or look for files handling avatar/image uploads.Affected if The function exists in the codebase, indicating the vulnerable code path is present
-
Test unauthenticated access to upload endpointUse a tool like curl to send a POST request to the upload endpoint (commonly at wp-admin/admin-ajax.php?action=mj_smgt_user_avatar_image_upload or similar) without providing authentication cookies.Affected if The endpoint responds without requiring login, allowing unauthenticated file upload attempts
If the School Management System plugin is installed at a version below 92.0.0 and the upload endpoint accepts unauthenticated requests, the environment is affected by this CVE.
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 · scoped92.0.0
Update the plugin to a patched version immediately. If no patch exists, disable the plugin or block unauthenticated access to the upload endpoint via WAF while awaiting a fix.
Version 92.0.0
- 1. Backup your WordPress site and database before making any changes.
- 2. Navigate to the WordPress admin dashboard.
- 3. Go to Plugins > Installed Plugins.
- 4. Find the 'School Management System' plugin.
- 5. If an update is available, click 'Update Now' to upgrade to version 92.0.0.
- 6. Alternatively, download version 92.0.0 from the WordPress plugin repository or CodeCanyon and upload it manually via Plugins > Add New > Upload Plugin.
- 7. Verify the update was successful by checking the plugin version.
- 8. Test the avatar upload functionality to confirm the file upload restriction is working properly.
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-9659 — 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-9659 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