CVE-2020-25411
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 · uneditedProjectworlds Online Examination System 1.0 is vulnerable to CSRF, which allows a remote attacker to delete the existing user.
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 confidenceThis is a Cross-Site Request Forgery (CSRF) vulnerability in Projectworlds Online Examination System 1.0. An attacker can craft a malicious HTML page that, when visited by an authenticated administrator, will silently submit a request to delete existing user accounts. Since the application does not validate the origin of delete-user requests or use anti-CSRF tokens, the attacker can perform unauthorized actions on behalf of the victim.
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.
-
Verify the installed version is 1.0Locate the application version identifier in the source code, about page, or admin panel of the Online Examination System. This is typically found in a version file, footer, or system info page.Affected if The installed version is exactly 1.0 and the application is the Projectworlds Online Examination System.
-
Identify the delete-user functionalityLocate the user deletion endpoint in the admin panel. Common paths include /delete-user, /user/delete, or similar admin action URLs that handle user account removal.Affected if The application has a user deletion feature accessible to administrators.
-
Inspect the delete-user form for anti-CSRF tokensView the HTML source of the delete-user form/page (e.g., via browser DevTools or by accessing the page source). Look for a hidden input field containing a token value, or check if the form submission includes any token parameter in the request.Affected if The delete-user form lacks a CSRF token parameter or the token is missing from the form markup.
-
Check session cookie SameSite attributeUsing browser DevTools, inspect the session cookie (PHPSESSID or similar) set by the application. Look for the SameSite attribute in the Set-Cookie header or cookie details.Affected if The session cookie does not have the SameSite attribute set, or it is set to None without Secure flag.
-
Verify Origin/Referer header validationSend a delete-user request with a mismatched or missing Origin/Referer header (e.g., using curl). Observe whether the server rejects the request or processes it regardless of the header value.Affected if The server processes delete-user requests without validating the Origin or Referer headers.
A user is affected if they run Online Examination System version 1.0 and the delete-user functionality lacks anti-CSRF tokens, proper Origin/Referer validation, 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 on all state-changing operations including user deletion, validate the Origin/Referer header server-side, and set SameSite attribute on session cookies to prevent cross-site request submission.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25411 — 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-25411 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