LiveActive security incident?Get immediate response
CVE Record

CVE-2014-125086: Gimmie Plugin trigger_login.php sql injection

A vulnerability has been found in Gimmie Plugin 1.2.2 on vBulletin and classified as critical. Affected by this vulnerability is an unknown functionality of the file trigger_login.php. The manipulation of the argument userid leads to sql injection. Upgrading to version 1.3.0 is able to address this issue. The patch is named fe851002d20a8d6196a5abb68bafec4102964d5b. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-220207.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2014-125086 is a SQL injection issue in Gimmie Plugin 1.2.2 for vBulletin. A user-controlled userid argument in trigger_login.php can affect database queries. The available sources name version 1.3.0 as the fixed release. No provided source shows active exploitation.

Executive priority

Prioritize remediation where vBulletin remains business-relevant or externally reachable. The risk is moderate because exploitation requires some access, but SQL injection can affect stored data and trust in the forum platform.

Technical view

The vulnerability is classified as CWE-89 SQL injection in trigger_login.php, triggered through the userid argument. CVSS 3.1 is 5.5 with adjacent attack vector, low complexity, low privileges, no user interaction, and limited confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely in vBulletin installations that still run Gimmie Plugin 1.2.2. The CVSS vector indicates adjacent-network access and low privileges are required, so actual risk depends on where the forum and plugin are reachable and who can authenticate.

Exploitation context

The source bundle does not include exploit evidence, KEV listing, or a public exploitation claim. Treat this as a known SQL injection flaw with a named patch, not as confirmed active exploitation.

Researcher notes

Evidence is thin: the affected functionality is described as unknown, but the vulnerable file, parameter, fixed version, CWE, and patch commit are named. Avoid expanding scope beyond Gimmie Plugin 1.2.2 unless local code review proves otherwise.

Mitigation direction

  • Inventory vBulletin sites for Gimmie Plugin 1.2.2.
  • Upgrade Gimmie Plugin to version 1.3.0.
  • Confirm the patch commit fe851002d20a8d6196a5abb68bafec4102964d5b is present.
  • If upgrade is blocked, check project guidance for supported compensating controls.

Validation and detection

  • Verify the installed Gimmie Plugin version on each vBulletin instance.
  • Check whether trigger_login.php exists in deployed plugin code.
  • Confirm userid handling matches the patched 1.3.0 codebase.
  • Review application logs for unusual access to trigger_login.php.
Prepared
Confidence
medium
Sources
6

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-125086 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
5Source 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-125086Attack 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
n/aGimmie Plugin1.2.2Listed
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.