CVE-2020-26006
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 · uneditedProject Worlds Online Examination System 1.0 is affected by Cross Site Scripting (XSS) via account.php.
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 · low confidenceThe Online Examination System 1.0 by Project Worlds contains a Cross Site Scripting vulnerability in the account.php component. The vulnerability allows injection of malicious scripts through unsanitized user input, likely in account-related fields.
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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 Online Examination System installationLocate the web application files and check for the presence of the 'Online Examination System' by Project Worlds. Look for typical installation paths like /var/www/html/, /www/, or C:\inetpub\wwwroot\. Identify the main directory containing the application.Affected if The application directory contains files from the Online Examination System by Project Worlds, version 1.0
-
Verify account.php existsCheck for the presence of account.php in the web application root or admin directory. Common paths may include /account.php, /admin/account.php, or /student/account.php depending on the installation structure.Affected if The file account.php exists in the application and is accessible via the web server
-
Identify user input points in account.phpOpen account.php in a text editor and examine the form fields that accept user input. Look for POST or GET parameters related to account details such as username, email, full name, or profile fields.Affected if account.php contains form fields or parameters that accept user-supplied data without obvious sanitization routines
-
Check for input validation or output encodingSearch the account.php source code for security functions such as htmlspecialchars(), strip_tags(), htmlentities(), or any input validation routines. Check if these functions are applied to user input before it is displayed back.Affected if User input is processed and displayed without proper sanitization or output encoding functions, or such functions are absent from the code
-
Test if application is live and accessibleAccess the account.php page through a web browser or curl command to confirm the application is running and the account functionality is active.Affected if The Online Examination System 1.0 is deployed and accessible, with account.php handling user account data
Your environment is affected if you have the Online Examination System 1.0 by Project Worlds installed and account.php processes user input without sanitization or output encoding.
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 input validation and output encoding for all user-supplied data in account.php. Apply context-appropriate escaping and consider implementing a Content Security Policy header.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26006 — 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-26006 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