LiveActive security incident?Get immediate response
CVE Record

CVE-2015-10070: copperwall Twiddit index.php sql injection

A vulnerability was found in copperwall Twiddit. It has been rated as critical. This issue affects some unknown processing of the file index.php. The manipulation leads to sql injection. The identifier of the patch is 2203d4ce9810bdaccece5c48ff4888658a01acfc. It is recommended to apply a patch to fix this issue. The identifier VDB-218897 was assigned to this vulnerability.

MediumCVSS 6.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2015-10070 is a SQL injection flaw in copperwall Twiddit's index.php. If an organization still runs the affected Twiddit code, an attacker could influence database queries and potentially read or alter limited data. The public record names a patch commit, but affected versions are not identified.

Executive priority

Treat as a moderate-priority legacy application risk. Prioritize quickly if Twiddit is business-facing, handles sensitive data, or cannot be patched. Otherwise, resolve through normal vulnerability management with explicit asset confirmation.

Technical view

The source bundle maps this issue to CWE-89 and CVSS 3.1 score 6.3. The vector is AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L. The vulnerable processing is in index.php, with remediation linked to commit 2203d4ce9810bdaccece5c48ff4888658a01acfc. Version and CPE data are absent.

Likely exposure

Likely exposure is narrow: systems running copperwall Twiddit with vulnerable index.php. The sources do not identify affected versions or CPEs. The CVSS vector lists adjacent attack vector, so confirm actual network reach before assuming internet-wide exposure.

Exploitation context

No provided source reports active exploitation, and this CVE is not listed as KEV in the bundle. Public vulnerability metadata and a patch reference exist, which can still help defenders and attackers identify vulnerable code.

Researcher notes

Evidence is sparse. The bundle identifies the product, vulnerable file, CWE, CVSS vector, and patch commit, but not affected versions, vulnerable parameters, deployment prevalence, or exploitation in the wild. Avoid broad exposure claims without local verification.

Mitigation direction

  • Identify any copperwall Twiddit deployments or bundled copies.
  • Apply the referenced patch commit or current vendor guidance.
  • Restrict network access to Twiddit until patch status is confirmed.
  • Retire the application if it is unused or unsupported.
  • Review database privileges used by Twiddit for least privilege.

Validation and detection

  • Confirm whether Twiddit exists in asset inventories or source repositories.
  • Compare deployed code against commit 2203d4ce9810bdaccece5c48ff4888658a01acfc.
  • Review index.php database handling for parameterized query use.
  • Check application and database logs for unusual index.php errors.
  • Document affected-version uncertainty in the vulnerability record.
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-10070 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
6.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:N/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
6.3CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L2.83.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.3Medium
CVSS 3.1 vector shape for CVE-2015-10070Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:N/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
copperwallTwidditn/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.