dbcve.org
School Management SystemWordPress extension · Dasinfomedia

CVE-2024-9660

HIGH · 8.8 CVSS v3.1 Published 2024-11-23
Fix available
A fix is available. Upgrade to 92.0.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 arbitrary file uploads due to missing file type validation in the mj_smgt_load_documets_new() and mj_smgt_load_documets() functions in all versions up to, and including, 91.5.0. This makes it possible for authenticated attackers, with Student-level access and above, 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 confidence

The School Management System WordPress plugin fails to validate file types in mj_smgt_load_documets_new() and mj_smgt_load_documets(), allowing authenticated users with Student-level privileges to upload arbitrary files including executable scripts. This missing validation enables remote code execution by uploading malicious PHP files or other payloads to the server.

MitigationImplement strict allowlist-based file type validation using both extension and MIME type checks, validate file contents (magic bytes), sanitize uploaded filenames, and store files outside the web root or use non-executable directory configurations.

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
School Management SystemWordPress extension
Affected:< 92.0.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify WordPress plugin installation
    Locate the School Management System plugin in wp-content/plugins/ directory or check via WordPress admin Plugins page
    Affected if The plugin is installed and active
  2. Determine installed plugin version
    Check plugin header in main PHP file or view version in WordPress admin plugin list
    Affected if Version number is less than 92.0.0
  3. Verify document upload function exists
    Search plugin code for functions mj_smgt_load_documets_new() and mj_smgt_load_documets() in source files
    Affected if These upload functions exist in the plugin code
  4. Confirm Student-level access to upload feature
    Review user role permissions or test with a Student-level account accessing document upload functionality
    Affected if Students can access and use the document upload feature
  5. Inspect file type validation in upload handlers
    Examine source code of mj_smgt_load_documets_new() and mj_smgt_load_documets() for file extension and MIME type validation logic
    Affected if No file type validation or allowlist checks are present before file save operations

If the School Management System plugin version is below 92.0.0 AND the document upload functionality is accessible to Student-level users without proper file type validation, the environment is affected by this CVE.

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
Upgrade available Upgrade to 92.0.0 or later
Fixed in 92.0.0
Interim mitigation

Implement strict allowlist-based file type validation using both extension and MIME type checks, validate file contents (magic bytes), sanitize uploaded filenames, and store files outside the web root or use non-executable directory configurations.

Recommended fix High confidence

92.0.0

  1. 1. Create a full backup of your WordPress site (database and files) before updating.
  2. 2. Navigate to the WordPress admin dashboard > Plugins > Installed Plugins.
  3. 3. Locate the 'School Management System' plugin in the list.
  4. 4. Click 'Update now' if an update is available, or manually upload version 92.0.0 from a trusted source (such as the original purchase source on codecanyon.net).
  5. 5. After updating to version 92.0.0, verify the plugin version in the plugins list confirms 92.0.0 is installed.
  6. 6. Test the document upload functionality to confirm the file type validation is now working properly.
  7. 7. Review user roles and permissions to ensure only trusted users have Student-level or higher access.

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

Fix this in School Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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