CVE-2020-37090
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 file upload vulnerability that allows students to upload arbitrary PHP files to the messaging system. Attackers can upload malicious PHP scripts through the message attachment feature, enabling remote code execution on the server.
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 an insecure file upload vulnerability in its messaging system that allows authenticated students to upload arbitrary PHP files as message attachments. Due to lack of proper file type validation and the storage location being within the webroot, uploaded malicious PHP scripts can be executed, enabling complete remote code execution on the server.
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 versionLocate the application version identifier in the admin panel, about page, or version file (commonly in /includes, /config, or footer files)Affected if Running version 1.0 of Arox School ERP Pro
-
Identify if messaging system is activeAccess the student messaging/communication module and verify it is enabled for usersAffected if The messaging system is accessible and functional for student users
-
Verify file upload capability in messagingNavigate to the message compose/attachment feature in the messaging module and confirm file upload is permittedAffected if Students can attach files to messages through the messaging system
-
Inspect upload directory configurationCheck the application configuration or server to determine where message attachments are stored (commonly in /uploads, /attachments, or /media subdirectories)Affected if Attachments are stored in a web-accessible directory
-
Check PHP execution permissionsReview web server configuration (e.g., .htaccess, nginx config) or upload directory settings to verify if PHP script execution is allowed in the attachment storage locationAffected if PHP files can be executed from the attachment storage directory
Affected if running School ERP Pro version 1.0 with the messaging file upload feature enabled and attachments stored in a web-accessible directory where PHP execution is permitted.
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 dataImmediately disable the message attachment feature or restrict uploads to safe file types only (whitelist approach). Store all uploads outside the webroot directory and disable script execution in any accessible upload directories. Implement proper server-side validation of file content, not just extensions.
- Consultation6.0 h
- Implementation20.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-37090 — 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-37090 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