LiveActive security incident?Get immediate response
CVE Record

CVE-2020-18263: PHP-CMS v1.0 was discovered to contain a SQL injection vulnerability in the component search.php via the se...

PHP-CMS v1.0 was discovered to contain a SQL injection vulnerability in the component search.php via the search parameter. This vulnerability allows attackers to access sensitive database information.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-18263 is a SQL injection issue in PHP-CMS v1.0 search functionality. If an exposed site runs this version, an attacker may be able to query sensitive database information through the search parameter. The source bundle does not name a patch, CVSS score, or confirmed active exploitation.

Executive priority

Prioritize remediation for internet-facing PHP-CMS v1.0 sites because the reported impact is sensitive database access. If no affected deployment exists, document that finding and continue monitoring because metadata is sparse.

Technical view

The CVE describes SQL injection in PHP-CMS v1.0, component search.php, via the search parameter. Impact is stated as access to sensitive database information. Metadata does not provide CWE, CPE, CVSS, authentication requirements, affected forks, or a fixed version.

Likely exposure

Exposure is most likely limited to public or internal PHP-CMS v1.0 deployments where search.php is reachable and the search parameter reaches database queries. Inventory may be difficult because the CVE metadata lacks CPE and vendor/product normalization.

Exploitation context

The bundle includes a public GitHub issue and CVE records, but no KEV listing and no cited evidence of active exploitation. Treat this as publicly disclosed and potentially easy to find in exposed legacy PHP applications, while avoiding assumptions beyond the sources.

Researcher notes

Evidence is thin: no CVSS, CWE, CPE, fixed version, or exploit-status detail is provided. The reliable technical claim is SQL injection in search.php through search. Further assessment should validate code exposure and seek upstream issue details without assuming broader product impact.

Mitigation direction

  • Check the upstream repository or vendor guidance for a fixed release or official workaround.
  • Remove or restrict access to search.php if the search feature is not required.
  • If maintaining the code, replace string-built SQL with parameterized queries.
  • Review database permissions so the web account has minimal required access.
  • Monitor web and database logs for abnormal search requests or SQL errors.

Validation and detection

  • Identify any PHP-CMS v1.0 deployments in asset inventory or source repositories.
  • Confirm whether search.php is reachable from untrusted networks.
  • Review search.php for unsafely constructed SQL using the search parameter.
  • Check application logs for unusual search activity and database error patterns.
  • Verify any update or code remediation in staging before production rollout.
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-18263 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.