LiveActive security incident?Get immediate response
CVE Record

CVE-2014-125058: LearnMeSomeCodes project3 search.rb search_first_name sql injection

A vulnerability was found in LearnMeSomeCodes project3 and classified as critical. This issue affects the function search_first_name of the file search.rb. The manipulation leads to sql injection. The patch is named d3efa17ae9f6b2fc25a6bbcf165cefed17c7035e. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-217607. NOTE: Maintainer is aware of this issue as remarked in the source code.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's Takemoderate

Analyst readout for executives and security teams

Plain-English summary

CVE-2014-125058 is a SQL injection issue in LearnMeSomeCodes project3. A vulnerable search function may let a low-privileged attacker affect database confidentiality, integrity, and availability at a limited level. This matters only where this specific project is deployed.

Executive priority

Treat as a moderate, targeted remediation item. Prioritize if this project is internet-adjacent, handles sensitive data, or shares a database with higher-value systems. Otherwise, confirm non-use and document that decision.

Technical view

The issue affects search_first_name in search.rb in LearnMeSomeCodes project3. Input manipulation leads to SQL injection, mapped to CWE-89. The CVSS v3.1 score is 5.5 with adjacent access, low attack complexity, low privileges, no user interaction, and low C/I/A impact.

Likely exposure

Exposure appears limited to organizations running LearnMeSomeCodes project3, especially deployments containing the vulnerable search.rb code path. The CVE data lists versions as n/a and provides no CPEs, so automated product matching may be unreliable.

Exploitation context

The source bundle does not indicate active exploitation, and KEV is false. CVSS indicates adjacent-network access and low privileges are required. Public sources identify the flaw class and patched commit, but do not provide evidence of broad real-world abuse.

Researcher notes

Evidence is narrow: VulDB, CVE records, and a GitHub patch reference. Versions are not specified, CPEs are absent, and the note says the maintainer was aware in source code. Validate against code state, not product inventory alone.

Mitigation direction

  • Inventory any deployed LearnMeSomeCodes project3 instances and confirm whether search.rb exists.
  • Apply commit d3efa17ae9f6b2fc25a6bbcf165cefed17c7035e or vendor-approved equivalent.
  • Restrict database privileges used by the application to the minimum required.
  • Review vendor or maintainer guidance before applying any non-standard workaround.

Validation and detection

  • Check repository history or deployed artifacts for the patch commit.
  • Review search.rb for parameterized handling in search_first_name.
  • Confirm logs show no unexpected database errors around search requests.
  • Run approved application security tests in a non-production environment.
Prepared
Confidence
medium
Sources
5

Based on public source material and reviewed before publication.

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-125058 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-125058Attack 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
LearnMeSomeCodesproject3n/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.