LiveActive security incident?Get immediate response
CVE Record

CVE-2018-25172: Pedidos 1.0 SQL Injection via load_proveedores.php

Pedidos 1.0 contains an SQL injection vulnerability that allows unauthenticated attackers to execute arbitrary SQL queries by injecting malicious code through the 'q' parameter. Attackers can send GET requests to the ajax/load_proveedores.php endpoint with crafted SQL payloads to extract sensitive database information including schema names and table structures.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Pedidos 1.0 has an unauthenticated SQL injection flaw in a supplier-loading endpoint. A remote attacker could query the application database and expose sensitive information such as schema and table details. The issue is high urgency for any organization still running this specific application version, especially if it is internet-facing.

Executive priority

Prioritize quickly if Pedidos 1.0 is internet-facing or contains sensitive business data. The vulnerability can expose database information without login. If the product is not present, no action is needed beyond confirming inventory.

Technical view

CVE-2018-25172 is CWE-89 SQL injection in Obedalvarado Pedidos 1.0. The vulnerable component is ajax/load_proveedores.php, where the q parameter can be manipulated by unauthenticated remote requests. The CVSS 4.0 score is 8.8, reflecting network access, low complexity, no privileges, no user interaction, high confidentiality impact, and limited integrity impact.

Likely exposure

Exposure appears limited to deployments of Obedalvarado Pedidos version 1.0. Risk is greatest where the application is reachable from untrusted networks. No other affected products or versions are identified in the provided sources.

Exploitation context

A public ExploitDB entry is referenced, indicating exploit information is publicly available. The source bundle does not show CISA KEV listing or confirmed active exploitation. Treat public-facing instances as higher risk because exploitation requires no authentication or user interaction.

Researcher notes

The available sources identify one affected version and endpoint, with CVSS 4.0 vector CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N. Do not infer broader product impact. Public exploit publication is not the same as confirmed in-the-wild exploitation.

Mitigation direction

  • Identify whether Obedalvarado Pedidos 1.0 is deployed anywhere in the environment.
  • Restrict external access to the Pedidos application until vendor guidance is confirmed.
  • Check vendor or project guidance for patches, maintained versions, or safe upgrade options.
  • Review database permissions used by the application and reduce unnecessary privileges.
  • Monitor application and database logs for suspicious requests to the affected endpoint.

Validation and detection

  • Inventory web applications and confirm any Pedidos installations and versions.
  • Check whether ajax/load_proveedores.php is reachable from untrusted networks.
  • Review access logs for unusual q parameter activity on the affected endpoint.
  • Use non-destructive vulnerability scanning where authorized to confirm exposure.
  • Verify compensating controls restrict unauthenticated access to the vulnerable path.
Prepared
Confidence
high
Sources
4

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-2018-25172 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
8.8 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/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
3Source 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
8.8CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:NPrimary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

8.8High
CVSS 4.0 vector shape for CVE-2018-25172Attack 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:H/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
ObedalvaradoPedidos1.0Listed
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.