CVE-2020-37089
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 · uneditedSchool ERP Pro 1.0 contains a SQL injection vulnerability in the 'es_messagesid' parameter that allows attackers to manipulate database queries through GET requests. Attackers can exploit the vulnerable parameter by injecting crafted SQL statements to potentially extract, modify, or delete database information.
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 confidenceSchool ERP Pro 1.0 has a critical SQL injection vulnerability in the 'es_messagesid' GET parameter. Attackers can inject arbitrary SQL statements through this parameter to manipulate database queries, potentially allowing unauthorized data extraction, modification, or deletion.
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= 1.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Confirm School ERP Pro installation and versionLocate the School ERP Pro installation directory or check version information files (such as version.php, about.php, or admin panel about section) to verify the installed version is 1.0Affected if The installed version is confirmed to be School ERP Pro version 1.0
-
Identify the messages module endpointLocate the PHP file that handles the 'es_messagesid' parameter by searching for 'es_messagesid' in the web application source code, typically found in message-related PHP files within the application directoryAffected if The code contains a handler for the 'es_messagesid' GET parameter without parameterized queries
-
Check if database queries use direct parameter concatenationReview the PHP code handling 'es_messagesid' - examine how the parameter is incorporated into SQL queries. Look for patterns like direct string concatenation ($sql = "SELECT * FROM... WHERE id=" . $_GET['es_messagesid']) instead of prepared statementsAffected if The code directly incorporates the 'es_messagesid' parameter into SQL queries without using prepared statements or parameter binding
-
Verify web server accessibility of vulnerable endpointConfirm the message-related pages are accessible on the web server by accessing URLs such as /messages.php, /message.php, or similar paths that might process the es_messagesid parameterAffected if The messages module is accessible and the es_messagesid parameter is processed by the application
The environment is affected if School ERP Pro version 1.0 is installed and the application processes the es_messagesid GET parameter through direct SQL query concatenation without prepared statements.
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.
From vendor dataFix by implementing parameterized queries or prepared statements for all database operations involving user input, combined with input validation and least-privilege database accounts.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-37089 — 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-2020-37089 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