CVE-2025-1669
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 SQL Injection via the 'addNotify' action in all versions up to, and including, 2.2.17 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 teacher-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 confidenceThe WPSchoolPress WordPress plugin versions up to 2.2.17 contain a SQL Injection vulnerability in the 'addNotify' action. Authenticated attackers with teacher-level access or higher can inject malicious SQL commands through insufficiently sanitized user input that is directly incorporated into SQL queries without proper escaping or prepared statements, potentially allowing extraction of sensitive database contents.
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<= 2.2.16CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm WPSchoolPress plugin is installedIn WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'WPSchoolPress' by Igexsolutions, or check the plugin files in /wp-content/plugins/wpschoolpress/ for the main PHP fileAffected if WPSchoolPress plugin is present on the WordPress site
-
Identify installed WPSchoolPress versionCheck the plugin header in the main WPSchoolPress PHP file (usually wpschoolpress.php) for the 'Version' comment, or view the plugin details in WordPress admin under Plugins > Installed PluginsAffected if The version is 2.2.16 or lower (any version up to and including 2.2.16)
-
Verify teacher-level user accounts existIn WordPress admin, go to Users and look for accounts with the 'Teacher' role specifically assigned by WPSchoolPress (check Users > WPSchoolPress Users if a custom user management interface exists), or query the wp_usermeta table for meta_value containing 'teacher'Affected if At least one user account with teacher-level privileges exists in the system
-
Confirm addNotify functionality is accessibleCheck if the WordPress REST API endpoint or AJAX handler for 'addNotify' action is active by reviewing the plugin's main PHP file for the function handling 'addNotify' (typically wp_ajax_wpschoolpress_addNotify or similar), or attempt a legitimate test request if you have teacher accessAffected if The addNotify action handler is registered and active in the plugin (present in versions 2.2.17 and below)
-
Review database query logs for suspicious addNotify activityEnable query logging in MySQL/MariaDB (general_log = 1) or check existing WAF/audit logs for requests to the addNotify endpoint containing SQL injection patterns such as quotes, UNION SELECT, or common SQL keywordsAffected if Any logs show unusual SQL syntax in addNotify requests that suggest exploitation attempts
A site is affected if WPSchoolPress version 2.2.16 or lower is installed with the addNotify feature active and teacher-level accounts exist on 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 · scopedUpdate the WPSchoolPress plugin to version 2.2.18 or later. If patching is delayed, restrict teacher-level account access and implement Web Application Firewall rules to detect SQL injection attack patterns.
WPSchoolPress version 2.2.18 or later
- 1. Log in to the WordPress admin dashboard with administrator privileges
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate the WPSchoolPress plugin in the list
- 4. If an update is available, click 'Update Now' to upgrade to the latest version
- 5. Alternatively, download the latest version from the WordPress Plugin Repository and upload it manually via Plugins > Add New > Upload Plugin
- 6. After updating, verify the plugin version is 2.2.18 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1669 — 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-1669 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