LiveActive security incident?Get immediate response
CVE Record

CVE-2020-37156: BloodX 1.0 - Authentication Bypass

BloodX 1.0 contains an authentication bypass vulnerability in login.php that allows attackers to access the dashboard without valid credentials. Attackers can exploit the vulnerability by sending a crafted payload with '=''or' parameters to bypass login authentication and gain unauthorized access.

MediumCVSS 6.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

BloodX 1.0 has an authentication bypass in its login page. An unauthenticated attacker could reach the dashboard without valid credentials. The issue is publicly documented and has an Exploit-DB reference, but the provided sources do not show active exploitation or a confirmed vendor patch.

Executive priority

Treat as a targeted application risk, not a broad enterprise emergency. Prioritize quickly if BloodX 1.0 supports sensitive operations or is internet-facing. If not deployed, no action is needed beyond documentation.

Technical view

CVE-2020-37156 affects diveshlunker BloodX 1.0. The flaw is CWE-288, an authentication bypass in login.php, reachable over the network with low complexity and no privileges or user interaction. CVSS v4.0 is 6.9. Impact is limited confidentiality and integrity loss, with no availability impact stated.

Likely exposure

Exposure is limited to organizations running BloodX 1.0, especially if the application is internet-accessible or reachable by untrusted users. The provided data does not identify other affected versions or packaged distributions.

Exploitation context

A public Exploit-DB entry exists, so defenders should assume the bypass technique is discoverable. However, the CVE is not marked KEV, and the supplied sources do not report active exploitation in the wild.

Researcher notes

Sources identify BloodX 1.0 only and describe an authentication bypass in login.php. No CPEs, patch version, or vendor remediation are provided. Avoid assuming impact beyond dashboard access and limited confidentiality/integrity effects stated by CVSS.

Mitigation direction

  • Identify and inventory any BloodX 1.0 deployments.
  • Remove public internet exposure where possible.
  • Restrict access to trusted networks or authenticated gateways.
  • Check the BloodX repository and advisory sources for vendor guidance.
  • Consider replacing or retiring BloodX if no maintained fix exists.

Validation and detection

  • Confirm whether BloodX is deployed and determine the installed version.
  • Review web server routes for exposed login.php instances.
  • Check access logs for unusual dashboard access without expected authentication patterns.
  • Verify network controls prevent untrusted access to BloodX.
  • Document whether any vendor update or remediation is available.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-288: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-37156 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.9 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.9CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NPrimary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

6.9Medium
CVSS 4.0 vector shape for CVE-2020-37156Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
diveshlunkerBloodX1.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-288 · source CWE mapping

Authentication Bypass Using an Alternate Path or Channel

Authentication Bypass Using an Alternate Path or Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.