LiveActive security incident?Get immediate response
CVE Record

CVE-2014-125047: tbezman school-store sql injection

A vulnerability classified as critical has been found in tbezman school-store. This affects an unknown part. The manipulation leads to sql injection. The identifier of the patch is 2957fc97054216d3a393f1775efd01ae2b072001. It is recommended to apply a patch to fix this issue. The identifier VDB-217557 was assigned to this vulnerability.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2014-125047 is an SQL injection issue in tbezman school-store. The public record does not identify the exact component or affected versions. Organizations running this project, a fork, or derived code should confirm whether the referenced patch is present because database confidentiality, integrity, and availability can be affected.

Executive priority

Treat as a targeted remediation item, not an emergency based on available evidence. Prioritize if the application stores sensitive records, is reachable by untrusted users, or exists in maintained production systems.

Technical view

The vulnerability is classified as CWE-89 SQL injection in tbezman school-store. The CVSS 3.1 vector is AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L, scoring 5.5. The public source identifies patch commit 2957fc97054216d3a393f1775efd01ae2b072001 but does not describe the vulnerable code path in detail.

Likely exposure

Exposure is most likely in self-hosted or forked deployments of tbezman school-store that predate the referenced patch. The source bundle lists versions as n/a and no CPEs, so asset matching requires repository or code-level confirmation.

Exploitation context

No CISA KEV listing is provided, and the sources do not state active exploitation. The CVSS vector indicates adjacent network access and low privileges are required, with no user interaction needed.

Researcher notes

Public evidence is sparse: unknown affected part, versions listed as n/a, and no exploit-status confirmation. Analysis should focus on comparing deployed code against the patch and documenting whether any reachable SQL construction remains unsafe.

Mitigation direction

  • Apply the referenced patch commit or update to a version containing it.
  • Check vendor or repository guidance for any additional remediation details.
  • Identify and remediate forks or customized copies with equivalent vulnerable code.
  • Restrict access to the application while remediation is pending.

Validation and detection

  • Inventory deployments and forks of tbezman school-store.
  • Confirm whether commit 2957fc97054216d3a393f1775efd01ae2b072001 is present.
  • Review application logs for database errors around input-handling paths.
  • Run regression tests covering affected request handling after patching.
Prepared
Confidence
medium
Sources
5

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-2014-125047 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
5.5 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2014-125047Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/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
tbezmanschool-storen/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.