LiveActive security incident?Get immediate response
CVE Record

CVE-2015-10041: Dovgalyuk AIBattle procedures.php sendComments sql injection

** UNSUPPORTED WHEN ASSIGNED ** A vulnerability classified as critical has been found in Dovgalyuk AIBattle. Affected is the function sendComments of the file site/procedures.php. The manipulation of the argument text leads to sql injection. The name of the patch is e3aa4d0900167641d41cbccf53909229f00381c9. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-218304. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2015-10041 is a SQL injection issue in unsupported Dovgalyuk AIBattle. A low-privileged user on an adjacent network could potentially affect confidentiality, integrity, and availability at a limited level. Business urgency depends on whether any legacy AIBattle deployment still exists.

Executive priority

Treat as a legacy exposure cleanup item. Prioritize quickly if AIBattle is still deployed in production or connected to sensitive databases.

Technical view

The reported flaw affects sendComments in site/procedures.php. Manipulation of the text argument can lead to SQL injection. The CVSS 3.1 score is 5.5 with adjacent attack vector, low complexity, low privileges required, and no user interaction.

Likely exposure

Exposure is likely limited to organizations still running the unsupported Dovgalyuk AIBattle codebase, especially where site/procedures.php is reachable by low-privileged users on adjacent networks.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. VulDB classifies the issue as critical, while the provided CVSS severity is medium.

Researcher notes

Evidence names the vulnerable argument and function but does not provide affected version ranges. Validate by code review and patch presence, not by offensive testing. Unsupported status increases remediation pressure.

Mitigation direction

  • Apply the referenced patch commit if maintaining AIBattle internally.
  • Retire or replace unsupported AIBattle deployments where possible.
  • Restrict access to any remaining AIBattle instance to trusted networks and users.
  • Check vendor repository guidance before making local remediation changes.

Validation and detection

  • Inventory systems for Dovgalyuk AIBattle or forks of AIBattle-disabled-.
  • Confirm whether site/procedures.php and sendComments exist in deployed code.
  • Verify the referenced patch commit is present where AIBattle remains deployed.
  • Confirm low-privileged users cannot reach the affected workflow unnecessarily.
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-10041 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-10041Attack 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
DovgalyukAIBattlen/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.