LiveActive security incident?Get immediate response
CVE Record

CVE-2017-20129: LogoStore search.php sql injection

A vulnerability was found in LogoStore. It has been classified as critical. Affected is an unknown function of the file /LogoStore/search.php. The manipulation of the argument query with the input test' UNION ALL SELECT CONCAT(CONCAT('qqkkq','VnPVWVaYxljWqGpLLbEIyPIHBjjjjASQTnaqfKaV'),'qvvpq'),NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL-- oCrh&search= leads to sql injection. It is possible to launch the attack remotely.

MediumCVSS 6.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2017-20129 is a SQL injection in LogoStore's /LogoStore/search.php search query handling. A remote authenticated user could potentially read or alter limited database data and affect availability. The public record does not identify affected versions, a vendor patch, or active exploitation.

Executive priority

Treat as a moderate-priority exposure review. Prioritize systems that are public-facing, handle sensitive data, or have weak account controls, but do not assume active exploitation from the supplied evidence.

Technical view

The issue is CWE-89 SQL injection via the query argument in /LogoStore/search.php. CVSS v3.1 is 6.3: network reachable, low complexity, privileges required, no user interaction, unchanged scope, and low confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to organizations running LogoStore with /LogoStore/search.php reachable to authenticated users. Affected vendor and version details are not specified, so inventory confirmation is necessary.

Exploitation context

The CVE states the attack can be launched remotely and requires privileges. It is not listed as KEV, and the supplied sources do not show confirmed active exploitation.

Researcher notes

Version and vendor metadata are incomplete. The public description includes an example injection pattern, but validation should focus on safe code review, configuration review, and log analysis rather than reproducing payloads.

Mitigation direction

  • Identify whether LogoStore is deployed and internet-accessible.
  • Check vendor or project guidance for supported fixes.
  • Restrict access to /LogoStore/search.php where possible.
  • Review input handling for parameterized database queries.
  • Monitor application and database logs for suspicious search activity.

Validation and detection

  • Inventory systems for LogoStore installations.
  • Confirm whether /LogoStore/search.php exists and is reachable.
  • Review application code for unsafe query concatenation.
  • Check authentication requirements around the search function.
  • Look for unusual search errors or database syntax failures in logs.
Prepared
Confidence
medium
Sources
3

Public sources used

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-2017-20129 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.3 (3.1)
Known Exploited
No
Published

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

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
6.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L2.83.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.3Medium
CVSS 3.1 vector shape for CVE-2017-20129Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
unspecifiedLogoStoren/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.