LiveActive security incident?Get immediate response
CVE Record

CVE-2025-52025: An SQL Injection vulnerability exists in the GetServiceByRestaurantID endpoint of the Aptsys gemscms POS Pl...

An SQL Injection vulnerability exists in the GetServiceByRestaurantID endpoint of the Aptsys gemscms POS Platform backend thru 2025-05-28. The vulnerability arises because user input is directly inserted into a dynamic SQL query syntax without proper sanitization or parameterization. This allows an attacker to inject and execute arbitrary SQL code by submitting crafted input in the id parameter, leading to unauthorized data access or modification.

CriticalCVSS 9.4Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2025-52025 is a critical SQL injection issue in the Aptsys gemscms POS Platform backend. An unauthenticated network attacker may be able to manipulate the id input to read or change backend data. The sources do not name a vendor patch, affected CPE, or confirmed exploitation.

Executive priority

Treat this as urgent for any internet-exposed or partner-exposed POS backend. The business risk is unauthorized access to or modification of operational data. Priority drops only if the product is not deployed or the endpoint is not reachable.

Technical view

The reported flaw is CWE-89 in the GetServiceByRestaurantID endpoint through 2025-05-28. User-controlled id input is inserted into dynamic SQL without proper sanitization or parameterization. CVSS 3.1 is 9.4: network exploitable, low complexity, no privileges, no user interaction, with high confidentiality and integrity impact.

Likely exposure

Exposure is likely limited to organizations running Aptsys gemscms POS Platform backend versions through 2025-05-28, especially if the backend endpoint is reachable from untrusted networks. The CVE metadata lacks normalized affected vendor, product, version, and CPE entries.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. The vulnerability characteristics are serious because unauthenticated SQL injection can enable unauthorized data access or modification, but exploit status should be treated as unconfirmed from the provided evidence.

Researcher notes

Evidence is materially incomplete: affected vendor/product fields are n/a, no CPEs are provided, and no patch information appears in the source bundle. The CVSS vector supports critical severity, but asset mapping and remediation confirmation require vendor or maintainer validation.

Mitigation direction

  • Check Aptsys or product maintainer guidance for a fixed release or official mitigation.
  • Restrict untrusted access to the affected backend endpoint where operationally feasible.
  • Review backend code for parameterized queries around GetServiceByRestaurantID id handling.
  • Increase monitoring for suspicious requests targeting the affected endpoint.
  • Prioritize backup integrity checks before making application or database changes.

Validation and detection

  • Inventory whether gemscms POS Platform backend is deployed in your environment.
  • Confirm whether deployments include the GetServiceByRestaurantID endpoint through 2025-05-28.
  • Review logs for unusual requests to GetServiceByRestaurantID and related database errors.
  • Verify whether id handling is parameterized or otherwise safely validated.
  • Document any compensating controls limiting endpoint reachability.
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-2025-52025 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
Critical
CVSS
9.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

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
9.4CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L3.95.5CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.4Critical
CVSS 3.1 vector shape for CVE-2025-52025Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
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.