LiveActive security incident?Get immediate response
CVE Record

CVE-2020-20474: White Shark System (WSS) 1.3.2 has a SQL injection vulnerability.

White Shark System (WSS) 1.3.2 has a SQL injection vulnerability. The vulnerability stems from the default_task_edituser.php files failing to filter the csa_to_user parameter. Remote attackers can exploit the vulnerability to obtain database sensitive information.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-20474 is a reported SQL injection in White Shark System 1.3.2. A remote attacker may be able to extract sensitive database information through insufficient filtering of one user-editing parameter. Public source detail is sparse, so confirm whether the product is actually deployed before escalating broadly.

Executive priority

Prioritize remediation for internet-facing or business-critical deployments because SQL injection can expose sensitive database data. If the system is not deployed, document non-exposure and close the item. The lack of CVSS and patch details makes local validation important.

Technical view

The CVE states that default_task_edituser.php does not filter the csa_to_user parameter in White Shark System 1.3.2, creating SQL injection exposure. No CVSS score, CWE mapping, vendor advisory, patch version, or CPE data is provided in the source bundle.

Likely exposure

Exposure is likely limited to organizations running White Shark System 1.3.2, especially where the affected user-editing PHP endpoint is reachable by untrusted users or the internet. The official affected metadata is incomplete and lists vendor, product, and CPE as n/a.

Exploitation context

The bundle includes a public GitHub reference, but no evidence of active exploitation. The CVE is not listed as KEV in the provided data. Treat public proof details as a validation signal, not proof of widespread exploitation.

Researcher notes

Key gaps are missing CVSS, CWE, CPE, vendor identity, and official remediation. The only technical detail in the bundle is the affected file and parameter. Do not assume other White Shark System versions are affected without additional evidence.

Mitigation direction

  • Identify whether White Shark System 1.3.2 is present in any environment.
  • Check maintainer or vendor guidance for patches or supported upgrade paths.
  • Restrict untrusted access to the affected user-editing endpoint.
  • Review application database privileges and reduce unnecessary access.
  • Monitor web and database logs for suspicious user-editing requests.

Validation and detection

  • Inventory public and internal web applications for White Shark System.
  • Confirm deployed version numbers against the reported 1.3.2 version.
  • Determine whether default_task_edituser.php is reachable by untrusted users.
  • Review logs for abnormal requests involving the csa_to_user parameter.
  • Check whether sensitive database tables are accessible to the application account.
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.

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-20474 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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