dbcve.org
InjectionWeakness · CWE-74

CVE-2025-15014

MEDIUM · 6.3 CVSS v3.1 Published 2025-12-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A security flaw has been discovered in loganhong php loganSite up to c035fb5c3edd0b2a5e32fd4051cbbc9e61a31426. This affects an unknown function of the file /includes/article_detail.php of the component Article Handler. Performing manipulation of the argument ID results in sql injection. It is possible to initiate the attack remotely. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in loganhong php loganSite's /includes/article_detail.php file via the ID parameter in the Article Handler component. An attacker can manipulate the ID argument to inject malicious SQL queries remotely.

MitigationImplement parameterized queries (prepared statements) for all database operations involving the ID parameter, or apply proper input validation and sanitization to prevent SQL injection attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm loganSite installation
    Locate the webroot directory and search for the file /includes/article_detail.php or look for files containing 'loganSite' or 'loganhong' in their headers or comments
    Affected if The file article_detail.php exists in the /includes directory of the web application
  2. Check if Article Handler is accessible
    Verify that the Article Handler component is reachable by attempting to access the article_detail.php script directly via HTTP/HTTPS request, or by reviewing web server routing configuration for routes that point to this file
    Affected if The article_detail.php script is accessible via the web server and processes incoming requests
  3. Verify ID parameter processing
    Examine the article_detail.php source code to confirm that the ID parameter is used directly in SQL queries without proper escaping, prepared statements, or input validation
    Affected if The ID parameter is concatenated directly into SQL queries without parameterized binding
  4. Test for SQL injection behavior
    Submit a crafted ID parameter value containing SQL metacharacters (such as a single quote) to the article_detail.php script and observe the application's response for SQL error messages or unexpected behavior
    Affected if The application returns database error messages or exhibits unusual behavior when special SQL characters are supplied in the ID parameter
  5. Review database user privileges
    Check the database configuration file used by loganSite to determine the privileges granted to the application database user
    Affected if The application database user has elevated privileges (such as file read/write, shell execution, or administrative rights) that could be exploited through successful SQL injection

A defender is affected if loganSite is installed, the article_detail.php file is web-accessible, and the ID parameter is processed without parameterized queries, enabling remote SQL injection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries (prepared statements) for all database operations involving the ID parameter, or apply proper input validation and sanitization to prevent SQL injection attacks.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-15014 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-15014 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data