WpschoolpressWordPress extension · Igexsolutions
CVE-2024-9637
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 – WPSchoolPress plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 2.2.10. This is due to the plugin not properly validating a user's identity prior to updating their details like email. This makes it possible for authenticated attackers, with teacher-level access and above, to change arbitrary user's email addresses, including administrators, and leverage that to reset the user's password and gain access to their account.
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 WPSchoolPress WordPress plugin fails to validate user identity before allowing email address changes. Authenticated attackers with teacher-level access or higher can modify email addresses of arbitrary users (including administrators) and then use the password reset function to take over those accounts.
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
< 2.2.11CVSS 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.
-
Verify WPSchoolPress plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'WPSchoolPress' by Igexsolutions in the list.Affected if Plugin is installed and active
-
Check installed plugin versionIn the Plugins list, click on 'WPSchoolPress' to view details or hover over the plugin row to see the version number. Compare against 2.2.11.Affected if Version is lower than 2.2.11
-
Identify users with teacher-level access or higherGo to Users section in WordPress admin. Review user roles - WPSchoolPress creates custom roles such as Teacher, Parent, or Student. Check for any accounts with elevated access beyond standard WordPress roles.Affected if Users with teacher-level roles exist and plugin version is below 2.2.11
-
Audit administrator accounts for unauthorized email changesReview user profiles in WordPress admin, focusing on administrator accounts. Check for any email addresses that were changed without authorization. Also review server access logs for POST requests to profile update endpoints.Affected if Administrator or other privileged accounts show unexpected email addresses
The environment is affected if the WPSchoolPress plugin version is below 2.2.11 and users with teacher-level or higher access exist in the system.
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 · scoped2.2.11
Update the plugin to version 2.2.11 or later. If an update is unavailable, disable the plugin and implement alternative access controls or remove the plugin entirely.
WPSchoolPress version 2.2.11
- Create a full backup of your WordPress site and database before making any changes
- Update the WPSchoolPress plugin to version 2.2.11 or later through the WordPress admin dashboard (Plugins > WPSchoolPress > Update) or via wp-cli: wp plugin update wpschoolpress
- Verify the plugin version was successfully updated to 2.2.11 or higher in the Plugins list
- Audit user accounts in WordPress admin (Users > All Users) to check for any unauthorized email address changes, particularly on administrator accounts
- As a precaution, reset passwords for all administrator accounts and any accounts with elevated privileges (teachers, staff)
- Review activity logs if available to identify any suspicious account takeover attempts that may have occurred prior to the update
- Consider implementing additional access controls or monitoring for the WPSchoolPress plugin
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wpschoolpress
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9637 — 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-9637 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