dbcve.org
WpschoolpressWordPress extension · Igexsolutions

CVE-2025-1668

MEDIUM · 5.4 CVSS v3.1 Published 2025-03-15
Fix available
A fix is available. Upgrade to after 2.2.16 or later.
See remediation →
60/100
Remediation priority · Elevated
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 – WPSchoolPress plugin for WordPress is vulnerable to arbitrary user deletion due to a missing capability check on the wpsp_DeleteUser() function in all versions up to, and including, 2.2.16. This makes it possible for authenticated attackers, with teacher-level access and above, to delete arbitrary user accounts.

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 WPSchoolPress WordPress plugin lacks proper capability validation in the wpsp_DeleteUser() function. While the plugin requires teacher-level authentication, it fails to verify whether the authenticated user has authorization to delete arbitrary accounts. This allows any authenticated user with teacher privileges or higher to delete any user in the WordPress system, including administrators.

MitigationUpdate to version 2.2.17 or later which implements proper capability checks on the deletion function, or disable the plugin until a patch is available.

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
WpschoolpressWordPress extension
Affected:<= 2.2.16

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
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

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 WPSchoolPress plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and locate 'WPSchoolPress' by Igexsolutions
    Affected if The WPSchoolPress plugin appears in the list of installed plugins
  2. Check installed version number
    In the Plugins list, view the version number displayed beneath the WPSchoolPress plugin name
    Affected if The version displayed is 2.2.16 or earlier
  3. Verify vulnerable function exists in codebase
    Access site files via FTP or file manager, locate the plugin directory (wp-content/plugins/wpschoolpress), and search for the wpsp_DeleteUser function definition in the plugin PHP files
    Affected if The function wpsp_DeleteUser is found in the plugin code without proper capability checks (look for missing current_user_can or wp_get_current_user validation before user deletion)
  4. Confirm teacher role has deletion access
    In WordPress admin, go to Users > Roles or examine the plugin role capabilities configuration to determine if teacher-level users have user deletion permissions
    Affected if Teacher role has permission to delete users system-wide or the role configuration allows deletion beyond the teacher's own students

A user is affected if the WPSchoolPress plugin version is 2.2.16 or earlier AND the wpsp_DeleteUser function lacks proper authorization checks, allowing any authenticated teacher to delete administrators.

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 a release after 2.2.16
Interim mitigation

Update to version 2.2.17 or later which implements proper capability checks on the deletion function, or disable the plugin until a patch is available.

Recommended fix Moderate confidence

Version 2.2.17 or latest available release on wordpress.org

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find WPSchoolPress in the plugin list
  4. If an update is available, click 'Update Now' to update to the latest version
  5. If no update is shown, manually download the latest version from wordpress.org/plugins/wpschoolpress and upload it via Plugins > Add New > Upload Plugin
  6. Verify the updated version is 2.2.17 or higher after updating

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

Fix this in Wpschoolpress Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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