LiveActive security incident?Get immediate response
CVE Record

CVE-2014-125046: Seiji42 cub-scout-tracker databaseAccessFunctions.js sql injection

A vulnerability, which was classified as critical, was found in Seiji42 cub-scout-tracker. This affects an unknown part of the file databaseAccessFunctions.js. The manipulation leads to sql injection. The patch is named b4bc1a328b1f59437db159f9d136d9ed15707e31. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-217551.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2014-125046 is a SQL injection issue in Seiji42 cub-scout-tracker. A user with some access on an adjacent network could potentially affect database confidentiality, integrity, and availability. The published details are sparse, but a specific patch commit is identified.

Executive priority

Treat as a targeted remediation item, not an emergency, unless this application stores sensitive member data or is accessible to untrusted users. Patch and verify during the next security maintenance cycle.

Technical view

The CVE describes CWE-89 SQL injection affecting an unspecified part of databaseAccessFunctions.js in Seiji42 cub-scout-tracker. CVSS 3.1 is 5.5 with adjacent-network attack vector, low complexity, low privileges required, no user interaction, and limited CIA impact.

Likely exposure

Exposure appears limited to organizations running Seiji42 cub-scout-tracker. Affected versions are not specified, and no CPEs are provided. Systems are higher priority if the application is reachable by untrusted local, campus, or partner-network users.

Exploitation context

The source bundle does not show active exploitation, and KEV status is false. VulDB classifies the issue as critical, while the CVE CVSS score is medium. No exploit procedure is needed to assess exposure.

Researcher notes

Evidence is limited: the bundle names the affected file and patch, but not vulnerable versions, exact code path, or public exploit status. Avoid broad product assumptions. Validate exposure by source review and deployment inventory.

Mitigation direction

  • Apply patch commit b4bc1a328b1f59437db159f9d136d9ed15707e31 where applicable.
  • Check vendor or repository guidance for any later fixes or release notes.
  • Restrict application access to trusted users and networks until patched.
  • Review database account permissions used by the application.
  • Back up the database before applying application changes.

Validation and detection

  • Inventory any cub-scout-tracker deployments or forks in use.
  • Confirm whether databaseAccessFunctions.js is present in deployed source.
  • Verify the identified patch commit or equivalent changes are applied.
  • Check application and database logs for unusual query errors or data changes.
  • Confirm no unsupported fork has reintroduced unsafe SQL handling.
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-125046 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-125046Attack 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
Seiji42cub-scout-trackern/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.