LiveActive security incident?Get immediate response
CVE Record

CVE-2015-10051: bony2023 Discussion-Board main.php display_all_replies sql injection

A vulnerability, which was classified as critical, has been found in bony2023 Discussion-Board. Affected by this issue is the function display_all_replies of the file functions/main.php. The manipulation of the argument str leads to sql injection. The patch is identified as 26439bc4c63632d63ba89ebc0f149b25a9010361. It is recommended to apply a patch to fix this issue. VDB-218378 is the identifier 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-10051 is a SQL injection flaw in bony2023 Discussion-Board. A user with some access could influence a reply-display parameter and affect the database. The source bundle names an upstream patch, but does not identify affected versions, real-world exploitation, or broad product adoption.

Executive priority

Treat as a targeted medium-risk web application issue. Patch promptly if this software is deployed, especially where external or semi-trusted users can access discussion-board functions.

Technical view

The issue is CWE-89 in functions/main.php, function display_all_replies. Manipulation of argument str can lead to SQL injection. CVSS 3.1 is 5.5: AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L. The bundle identifies patch commit 26439bc4c63632d63ba89ebc0f149b25a9010361.

Likely exposure

Exposure appears limited to organizations running bony2023 Discussion-Board or derived forks. The bundle lists versions as n/a, so defenders must verify code presence directly rather than rely on version matching.

Exploitation context

The source bundle does not support active exploitation: KEV is false and no cited source states exploitation in the wild. The public VulDB entry and patch make the flaw visible, but exploit availability is not established here.

Researcher notes

Evidence is narrow: VulDB and CVE data name the vulnerable function, argument, CWE, CVSS vector, and patch. Affected versions are not provided, so code-level verification is the defensible exposure method.

Mitigation direction

  • Apply the upstream patch identified by commit 26439bc4c63632d63ba89ebc0f149b25a9010361.
  • Check project or vendor guidance for any supported release containing the fix.
  • Review local forks for equivalent vulnerable display_all_replies code.
  • Prioritize remediation where the board is reachable by untrusted authenticated users.

Validation and detection

  • Inventory any bony2023 Discussion-Board deployments or forks.
  • Compare functions/main.php with the referenced patch commit.
  • Confirm str handling no longer reaches SQL construction unsafely.
  • Review application logs for unusual reply-display database errors.
  • Document whether exposure matches the CVSS adjacent-network and low-privilege assumptions.
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-10051 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-10051Attack 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
bony2023Discussion-Boardn/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.