dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-3740

HIGH · 8.8 CVSS v3.1 Published 2025-07-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Local File Inclusion in all versions up to, and including, 93.1.0 via the 'page' parameter. This makes it possible for authenticated attackers, with Subscriber-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included. The Local File Inclusion exploit can be chained to include various dashboard view files in the plugin. One such chain can be leveraged to update the password of Super Administrator accounts in Multisite environments making privilege escalation possible. The vendor has updated the version numbers beginning with `1.93.1 (02-07-2025)` for the patched version. This version comes after version 93.1.0.

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 for WordPress plugin has a Local File Inclusion vulnerability in all versions up to 93.1.0, exploitable through the 'page' parameter. Authenticated attackers with Subscriber-level access can include and execute arbitrary files on the server, leading to code execution. In Multisite installations, this can be chained to update Super Administrator passwords, achieving privilege escalation.

MitigationUpdate to version 1.93.1 or later. If immediate patching is not possible, restrict subscriber-level account creation and implement validation on the 'page' parameter to prevent path traversal.

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 checks

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

  1. Confirm School Management System plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'School Management System' or check the plugins directory for the presence of the /school-management/ folder
    Affected if The plugin appears in the installed plugins list
  2. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and click on the School Management System plugin to view its version, or inspect the main plugin PHP file for the 'Version' header comment
    Affected if The version listed is 93.1.0 or lower (any version up to and including 93.1.0 is affected)
  3. Verify if subscriber-level user accounts exist
    In WordPress admin, go to Users and examine the role column; look for any users with the 'Subscriber' role
    Affected if At least one user with Subscriber role exists in the system
  4. Check if WordPress is configured as Multisite
    Inspect the wp-config.php file in the WordPress root directory for the line 'define( "MULTISITE", true );' or check Network Admin menu presence in the admin sidebar
    Affected if WordPress Multisite is enabled (this increases exploit severity for privilege escalation)
  5. Inspect the vulnerable page parameter handling
    Review the plugin's main PHP files (typically in the includes/ or controllers/ folder) for code that uses the 'page' parameter in include/require statements without proper sanitization, such as include($_GET['page'])
    Affected if The code contains unsanitized include/require statements using the 'page' GET parameter

If the School Management System plugin is installed at version 93.1.0 or lower and subscriber-level accounts exist, the environment is vulnerable to CVE-2025-3740.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 1.93.1 or later. If immediate patching is not possible, restrict subscriber-level account creation and implement validation on the 'page' parameter to prevent path traversal.

Recommended fix High confidence

1.93.1 or later

  1. Backup the WordPress site and database before performing any updates
  2. Update the School Management System plugin to version 1.93.1 or later through the WordPress admin dashboard (Plugins > Updates or directly from the plugin page)
  3. Verify the update was successful by checking the installed plugin version
  4. Confirm that the 'page' parameter is now properly sanitized and path traversal is no longer possible

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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