LiveActive security incident?Get immediate response
CVE Record

CVE-2013-10012: antonbolling clan7ups Login/Session sql injection

A vulnerability, which was classified as critical, was found in antonbolling clan7ups. Affected is an unknown function of the component Login/Session. The manipulation leads to sql injection. The name of the patch is 25afad571c488291033958d845830ba0a1710764. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-218388.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2013-10012 is a SQL injection issue in the Login/Session component of antonbolling clan7ups. A successful attacker could affect limited confidentiality, integrity, and availability of application data. The public record is sparse, and affected versions are not identified.

Executive priority

Treat as a targeted remediation item if clan7ups is in use. The business urgency is moderate because the vulnerability affects data security, but public evidence suggests constrained attack prerequisites and no confirmed active exploitation.

Technical view

The CVE maps to CWE-89 SQL Injection in an unknown Login/Session function. CVSS 3.1 is 5.5 with adjacent attack vector, low complexity, low privileges required, no user interaction, and low CIA impacts. The named patch is commit 25afad571c488291033958d845830ba0a1710764.

Likely exposure

Exposure appears limited to organizations running antonbolling clan7ups, especially unpatched deployments reachable by adjacent-network users with low privileges. The source bundle does not identify affected versions, deployment prevalence, or internet exposure.

Exploitation context

The sources do not show CISA KEV listing or active exploitation. CVSS indicates exploitation requires adjacent network access and low privileges, with no user interaction. No exploit steps should be inferred from the public summary.

Researcher notes

Key gaps are affected versions, exact vulnerable function, exploit maturity, and operational prevalence. Validation should focus on code provenance and whether local forks include the referenced patch, without assuming broader product impact beyond antonbolling clan7ups.

Mitigation direction

  • Apply or verify the GitHub patch commit 25afad571c488291033958d845830ba0a1710764.
  • Check vendor or repository guidance for any later security updates.
  • Restrict access to clan7ups administrative or authenticated surfaces where feasible.
  • Review database permissions used by the application for least privilege.

Validation and detection

  • Inventory any deployed antonbolling clan7ups instances or forks.
  • Confirm deployed code contains the referenced patch commit or equivalent fix.
  • Review Login/Session database handling for parameterized queries.
  • Check logs for unusual login/session database errors or unauthorized 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-2013-10012 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-2013-10012Attack 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
antonbollingclan7upsn/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.