CVE-2025-6079
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 homework.php file in all versions up to, and including, 93.2.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. CVE-2025-31100 is potentially a duplicate of this.
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 fails to validate file types in homework.php, allowing authenticated users with Student-level permissions to upload arbitrary files. This arbitrary file upload can be leveraged to achieve remote code execution on the affected WordPress installation.
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
- 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.
-
Confirm School Management System plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'School Management System' or check the plugins directory for the school-management-system folderAffected if The plugin is installed and active
-
Identify the installed plugin versionCheck the plugin's main PHP file header (usually in wp-content/plugins/school-management-system/) for the Version comment, or look at the plugin details in WordPress admin plugin listAffected if The version is unpatched (any version prior to vendor release of a fix)
-
Locate the homework.php vulnerable fileCheck if homework.php exists in the plugin directory (wp-content/plugins/school-management-system/include/homework.php or similar path)Affected if The file exists and is web-accessible
-
Verify Student-level user role has upload permissionsIn WordPress admin, go to Users > Roles or check the role capabilities; look for Student role and verify if it has 'upload_files' capabilityAffected if Student role has upload_files capability enabled
-
Inspect upload directories for suspicious PHP filesCheck the wp-content/uploads/school/ directory (or wherever the plugin stores homework attachments) for .php, .php5, .phtml, or other executable file extensionsAffected if Any unexpected PHP files are present in upload directories
You are affected if the School Management System plugin is installed, the homework.php file exists, and Student-level users have file upload permissions that allow executable file uploads.
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.
From vendor dataUpdate the plugin to version 93.2.1 or later, which should include proper file type validation. Until patched, restrict Student-level account creation and monitor uploads directory for suspicious files.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6079 — 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-2025-6079 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