LiveActive security incident?Get immediate response
CVE Record

CVE-2020-21486: SQL injection vulnerability in PHPOK v.5.4.

SQL injection vulnerability in PHPOK v.5.4. allows a remote attacker to obtain sensitive information via the _userlist function in framerwork/phpok_call.php file.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-21486 is a reported SQL injection in PHPOK v5.4. A remote attacker could obtain sensitive information through the _userlist function in framerwork/phpok_call.php. The business risk is data exposure from affected public PHPOK deployments, but the provided sources do not identify a confirmed fix or active exploitation.

Executive priority

Prioritize any public PHPOK v5.4 systems because the reported impact is sensitive information disclosure without authentication. If PHPOK is not used, risk is negligible. If it is used, require rapid owner confirmation and a vendor-guidance-based remediation plan.

Technical view

The CVE describes CWE-89 SQL injection in PHPOK v5.4, reachable remotely with low complexity and no privileges or user interaction per CVSS 3.1. Impact is limited to confidentiality in the record, with high confidentiality impact and no stated integrity or availability impact.

Likely exposure

Exposure is most likely on internet-facing PHPOK v5.4 installations where the vulnerable _userlist functionality in framerwork/phpok_call.php is reachable. The source bundle does not provide CPEs, vendor metadata, or affected ranges beyond v5.4.

Exploitation context

The issue is publicly referenced in a GitHub issue, but the bundle marks KEV as false and provides no cited evidence of active exploitation. Treat it as publicly disclosed and potentially discoverable, not confirmed exploited.

Researcher notes

Evidence is sparse: the CVE record names PHPOK v5.4, _userlist, and framerwork/phpok_call.php, with CVSS 7.5. No affected CPEs, patch version, exploit maturity, or mitigation details are included in the provided bundle.

Mitigation direction

  • Inventory PHPOK deployments and identify any v5.4 instances.
  • Check the PHPOK project issue and vendor guidance for confirmed fixes.
  • Restrict external access to affected PHPOK functionality where practical.
  • Apply least-privilege database permissions for PHPOK application accounts.
  • Monitor web and database logs for suspicious query behavior.

Validation and detection

  • Confirm whether PHPOK v5.4 is present in production or staging.
  • Verify whether framerwork/phpok_call.php and _userlist functionality are reachable externally.
  • Review logs for unusual requests targeting PHPOK call functionality.
  • Use authorized SQL injection testing tools in a controlled validation window.
  • Document compensating controls if no vendor fix is available.
Prepared
Confidence
medium
Sources
3

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 · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration 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-21486 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A: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
2Source 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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2020-21486Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.