CVE-2020-36064
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 · uneditedOnline Course Registration v1.0 was discovered to contain hardcoded credentials in the source code which allows attackers access to the control panel if compromised.
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 · moderate confidenceOnline Course Registration v1.0 contains hardcoded credentials embedded directly in the source code. Attackers who discover these credentials (through code leaks, repository access, or reverse engineering) can bypass authentication and gain administrative access to the control panel.
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 Online Course Registration v1.0 is deployedIdentify any instance of the Online Course Registration application in your environment. Check web servers, application directories, or hosted platforms for this specific version (1.0).Affected if The application version 1.0 is present in your environment.
-
Locate source code filesFind the application source code on your systems. Search for PHP, HTML, JavaScript, or config files related to the Online Course Registration project.Affected if Source code files for this application exist in your environment.
-
Search for hardcoded credentials in source codeInspect the source code for embedded credentials such as hardcoded usernames, passwords, API keys, or database connection strings. Look in configuration files, authentication modules, and login-related code files.Affected if Hardcoded credentials (usernames, passwords, keys, or secrets) are found directly embedded in any source code files.
-
Verify authentication can be bypassedTest whether authentication can be circumvented using known or easily discoverable credentials. Attempt to access the administrative control panel using default, blank, or commonly guessable credentials found in the code.Affected if Administrative access to the control panel can be gained using hardcoded credentials found in the source code.
Your environment is affected if Online Course Registration v1.0 is deployed AND hardcoded credentials are present in the source code that allow bypassing authentication to the administrative panel.
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 dataRemove all hardcoded credentials from the source code and implement secure credential management such as environment variables, a secrets vault, or encrypted configuration files. Immediately rotate any credentials that may have been exposed.
- 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-36064 — 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-36064 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