LiveActive security incident?Get immediate response
CVE Record

CVE-2014-125041: Miccighel PR-CWT sql injection

A vulnerability classified as critical was found in Miccighel PR-CWT. This vulnerability affects unknown code. The manipulation leads to sql injection. The patch is identified as e412127d07004668e5a213932c94807d87067a1f. It is recommended to apply a patch to fix this issue. VDB-217486 is the identifier assigned to this vulnerability.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Miccighel PR-CWT has a SQL injection vulnerability. An authenticated user on an adjacent network may be able to affect limited confidentiality, integrity, and availability. Public sources identify a patch commit, but do not name the vulnerable component or affected versions.

Executive priority

Treat as a targeted remediation item, not a broad emergency. Prioritize confirmation if PR-CWT is used in production or reachable by semi-trusted users. Patch verification should be scheduled promptly because SQL injection can affect data integrity and confidentiality.

Technical view

CVE-2014-125041 is CWE-89 SQL injection in Miccighel PR-CWT, tracked by VulDB as VDB-217486. CVSS 3.1 is 5.5 with adjacent attack vector, low complexity, low privileges, no user interaction, and low C/I/A impact. The source bundle does not identify the vulnerable code path.

Likely exposure

Exposure is likely limited to organizations running Miccighel PR-CWT, especially reachable by adjacent network users. Version data is listed as n/a, so teams must identify deployments by product use and code state rather than version matching.

Exploitation context

The bundle does not show KEV listing or cited active exploitation. Public references classify the issue as critical in VulDB, but the supplied CVSS and prerequisites indicate moderate operational risk unless PR-CWT is exposed to untrusted adjacent users.

Researcher notes

Evidence is thin: affected versions and vulnerable code are not disclosed in the bundle. The CVSS vector suggests exploitation requires adjacent access and low privileges. Avoid assuming internet-wide exposure or active exploitation without additional vendor, KEV, or telemetry evidence.

Mitigation direction

  • Check whether any environment uses Miccighel PR-CWT.
  • Apply or verify patch commit e412127d07004668e5a213932c94807d87067a1f.
  • Review vendor or project guidance for any additional fixed releases.
  • Restrict PR-CWT access to trusted users and networks until verified fixed.

Validation and detection

  • Inventory repositories, deployments, and dependencies for Miccighel PR-CWT.
  • Compare installed code against the referenced patch commit.
  • Confirm access controls limit adjacent-network and low-privileged user reachability.
  • Review application and database logs for unusual query errors or data changes.
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-125041 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-125041Attack 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
MiccighelPR-CWTn/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.