dbcve.org
TeachpressWordPress extension · Mtrv

CVE-2025-32149

HIGH · 8.8 CVSS v3.1 Published 2025-04-04
Fix available
A fix is available. Upgrade to 9.0.12 or later.
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in winkm89 teachPress teachpress allows SQL Injection.This issue affects teachPress: from n/a through <= 9.0.11.

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

SQL injection vulnerability in teachPress plugin allows attackers to inject malicious SQL commands through unsanitized user inputs. The flaw stems from improper neutralization of special elements in SQL queries, potentially enabling unauthorized database access, data exfiltration, or manipulation.

MitigationUpdate to the patched version of teachPress. If no patched version is available, implement parameterized queries/ prepared statements for all database operations and sanitize all user-supplied input before incorporating it into SQL queries.

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
TeachpressWordPress extension
Affected:< 9.0.12

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. Check teachPress plugin version in WordPress
    Navigate to WordPress admin > Plugins > Installed Plugins > TeachPress. The version number is displayed below the plugin name. Alternatively, check the main plugin file (teachpress.php) or readme.txt for the 'Version' header.
    Affected if Version is displayed as less than 9.0.12
  2. Verify plugin is active
    In WordPress admin > Plugins, confirm the TeachPress plugin status shows 'Active'. Only active plugins process user input and can be exploited.
    Affected if Plugin is active and version is below 9.0.12
  3. Identify user input entry points
    TeachPress handles course enrollments, publications, and user submissions. Check if public-facing forms (enrollment forms, submission forms) are enabled in plugin settings under TeachPress > Settings.
    Affected if Public-facing TeachPress features are enabled and plugin version is vulnerable
  4. Confirm database access method
    Inspect TeachPress PHP files (particularly in includes/ directory) for direct SQL queries using $wpdb->prepare without proper sanitization, or queries using $wpdb->query with unsanitized $_POST/$_GET/$_REQUEST inputs.
    Affected if Custom SQL queries exist without prepared statements and plugin version is below 9.0.12

You are affected if TeachPress version is below 9.0.12, the plugin is active, and user-supplied input can reach database query functions.

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 9.0.12 or later
Fixed in 9.0.12
Interim mitigation

Update to the patched version of teachPress. If no patched version is available, implement parameterized queries/ prepared statements for all database operations and sanitize all user-supplied input before incorporating it into SQL queries.

Recommended fix High confidence

teachpress 9.0.12

  1. 1. Back up your current teachpress installation and database before proceeding
  2. 2. Download teachpress version 9.0.12 from the official WordPress plugin repository or the developer's website
  3. 3. Deactivate the current teachpress plugin through WordPress admin panel
  4. 4. Replace the existing teachpress files with the new version 9.0.12 files
  5. 5. Reactivate the teachpress plugin
  6. 6. Verify the plugin is running version 9.0.12 in the WordPress plugins admin area
  7. 7. Test critical functionality (creating courses, managing submissions, database operations) to ensure the upgrade did not break existing features

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

Fix this in Teachpress Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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