LiveActive security incident?Get immediate response
CVE Record

CVE-2015-10060: MNBikeways database views.py sql injection

A vulnerability was found in MNBikeways database and classified as critical. This issue affects some unknown processing of the file Data/views.py. The manipulation of the argument id1/id2 leads to sql injection. The identifier of the patch is 829a027aca7c17f5a7ec1addca8dd5d5542f86ac. It is recommended to apply a patch to fix this issue. The identifier VDB-218417 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-2015-10060 is a SQL injection issue in MNBikeways database. A low-privileged user on an adjacent network could manipulate id1 or id2 inputs and potentially read, change, or disrupt limited database data. Public sources name a patch commit but do not define affected versions.

Executive priority

Treat as a targeted internal-application risk, not an emergency internet-wide event. Prioritize patching if MNBikeways/database is deployed in any trusted, shared, or sensitive environment because SQL injection can affect data confidentiality, integrity, and availability.

Technical view

The vulnerability is CWE-89 in Data/views.py, where id1/id2 argument handling can lead to SQL injection. The CVSS 3.1 score is 5.5 with adjacent-network access, low privileges, no user interaction, unchanged scope, and low confidentiality, integrity, and availability impact.

Likely exposure

Exposure appears limited to deployments of MNBikeways/database code containing the vulnerable Data/views.py before patch commit 829a027aca7c17f5a7ec1addca8dd5d5542f86ac. The source bundle does not identify affected version numbers or package distribution channels.

Exploitation context

The source bundle does not report active exploitation, and the CVE is not listed as KEV. The CVSS vector indicates exploitation requires adjacent-network access and low privileges, which lowers broad internet-scale urgency but still matters for internal or shared environments.

Researcher notes

Evidence is sparse: product versions are unspecified, the vulnerable processing is described only as in Data/views.py, and public sources name the patch commit. Do not infer broader products, exploitation in the wild, or alternate fixes beyond vendor guidance and the referenced patch.

Mitigation direction

  • Apply commit 829a027aca7c17f5a7ec1addca8dd5d5542f86ac or a vendor release containing it.
  • Inventory deployed forks or copies of MNBikeways/database.
  • Restrict access to affected views until patched.
  • Review application logs for unusual requests involving id1 or id2 parameters.

Validation and detection

  • Confirm deployed code includes the referenced patch commit.
  • Check Data/views.py no longer builds SQL from raw id1 or id2 values.
  • Run authenticated regression tests for affected views after patching.
  • Verify no vulnerable unpatched copies remain in production or staging.
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-2015-10060 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-2015-10060Attack 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
MNBikewaysdatabasen/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.