CVE-2020-25408
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 · uneditedA Cross-Site Request Forgery (CSRF) vulnerability exists in ProjectWorlds College Management System Php 1.0 that allows a remote attacker to modify, delete, or make a new entry of the student, faculty, teacher, subject, scores, location, and article data.
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 confidenceA CSRF vulnerability in ProjectWorlds College Management System Php 1.0 allows remote attackers to forge authenticated requests, enabling unauthorized modification, deletion, or creation of records across multiple data entities including students, faculty, teachers, subjects, scores, locations, and articles.
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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 the installed product and versionAccess the admin panel, footer, or about page of the College Management System and identify if it is ProjectWorlds College Management System version 1.0Affected if The application is ProjectWorlds College Management System version 1.0
-
Inspect student management forms for CSRF tokensView the HTML source of add/edit student forms (typically at /student.php or similar) and search for a hidden input field containing a random token valueAffected if No hidden CSRF token field is present in student modification forms
-
Inspect faculty/teacher management forms for CSRF tokensView the HTML source of faculty or teacher creation/modification forms and check for a hidden token fieldAffected if No hidden CSRF token field is present in faculty or teacher forms
-
Check cookie configuration for SameSite attributeUse browser dev tools or intercept an HTTP response to inspect the Set-Cookie header for session cookies and verify if SameSite attribute is set to 'Strict' or 'Lax'Affected if SameSite attribute is missing or set to 'None' on session cookies
-
Verify server-side CSRF token validation existsExamine the PHP source code handling form submissions (e.g., student_add.php, faculty_add.php) to see if the submitted token is validated against a stored value before processingAffected if No server-side code validates CSRF tokens on state-changing operations
-
Inspect subject, score, and article management formsView HTML source of forms for managing subjects, scores, or articles to check for hidden CSRF token fieldsAffected if No hidden CSRF token fields are present in these state-changing forms
You are affected if you run College Management System version 1.0 and the application lacks CSRF tokens in forms and SameSite cookie attributes.
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 dataImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations and configure SameSite cookie attributes to prevent cross-origin request forgery.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25408 — 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-25408 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