dbcve.org
WpschoolpressWordPress extension · Igexsolutions

CVE-2024-12332

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-07
Fix available
A fix is available. Upgrade to after 2.2.14 or later.
See remediation →
71/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 SQL Injection via the 'cid' parameter in all versions up to, and including, 2.2.14 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Student/Parent-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 versions up to 2.2.14 contain a SQL injection vulnerability in the 'cid' parameter. Due to insufficient input sanitization and lack of prepared statements, authenticated attackers with Student/Parent-level access can inject malicious SQL queries to extract sensitive database information.

MitigationUpdate the WPSchoolPress plugin to a version beyond 2.2.14 when available. Until then, implement parameterized queries using $wpdb->prepare() for all SQL queries utilizing the 'cid' parameter and validate that user roles meet the minimum requirement for access.

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.14

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

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

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. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > WPSchoolPress and note the version number displayed. Alternatively, check the plugin header in wp-content/plugins/wpschoolpress/wpschoolpress.php for the Version field.
    Affected if The installed version is 2.2.14 or lower.
  2. Verify plugin is active
    Confirm the WPSchoolPress plugin is currently activated in the WordPress site. Check the Plugins page for an 'Active' status indicator.
    Affected if The plugin is active and the version is <= 2.2.14.
  3. Identify Student/Parent user accounts
    In WordPress admin, go to Users and review the list for any accounts assigned the Student or Parent role. Note the number of these accounts and their permissions.
    Affected if Student or Parent role accounts exist with access to the plugin.
  4. Locate vulnerable code references to cid parameter
    Inspect plugin files for SQL queries using the 'cid' parameter without $wpdb->prepare(). Search plugin PHP files for direct query patterns like 'SELECT' or 'INSERT' combined with 'cid' in the code.
    Affected if SQL queries referencing 'cid' exist without prepared statements.
  5. Review access controls on vulnerable endpoints
    Check if Student/Parent roles can access pages or functions that process the 'cid' parameter. Examine capability checks in the plugin code.
    Affected if Student/Parent roles can access endpoints that process the 'cid' parameter.
  6. Check server logs for SQL injection patterns
    Review web server access logs and WordPress debug logs for suspicious requests containing SQL keywords (UNION, SELECT, WHERE) in the cid parameter value.
    Affected if Logs show SQL injection attempts targeting the cid parameter.

You are affected if the WPSchoolPress plugin version is 2.2.14 or lower, the plugin is active, and Student/Parent-level accounts can access functionality that uses the 'cid' parameter without prepared statements.

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.14
Interim mitigation

Update the WPSchoolPress plugin to a version beyond 2.2.14 when available. Until then, implement parameterized queries using $wpdb->prepare() for all SQL queries utilizing the 'cid' parameter and validate that user roles meet the minimum requirement for access.

Recommended fix Moderate confidence

Latest version after 2.2.14 (verify in WordPress plugin repository)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate WPSchoolPress plugin
  4. Check if an update is available and update to the latest version

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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