CVE-2025-15014VulnerabilityPublished 22 Dec 2025

CVE-2025-15014: loganhong php loganSite · SQL Injection

Affects loganhong php loganSiteSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2025-15014, organizations should: 1) Immediately audit php loganSite installations to identify if the affected commit or similar vulnerable code is in use. 2) Implement strict input validation and sanitization for the 'ID' parameter in /includes/article_detail.php, ensuring only expected numeric or safe values are accepted. 3) Refactor database queries to use parameterized statements or prepared queries to prevent SQL injection. 4) Monitor database logs for unusual or suspicious queries indicative of injection attempts. 5) Restrict database user privileges to the minimum necessary to limit impact if exploited. 6) Follow vendor advisories for patches or updates, and apply them promptly once available. 7) Consider deploying web application firewalls (WAFs) with rules targeting SQL injection patterns specific to this vulnerability. 8) Conduct regular security assessments and code reviews focusing on input handling in custom or third-party CMS components. 9) Educate developers and administrators on secure coding practices related to database interactions.

Description

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.

Impact

For European organizations using php loganSite, this vulnerability poses a risk of unauthorized data disclosure, data manipulation, and potential service disruption. Attackers exploiting the SQL injection could access sensitive information stored in the database, such as user credentials, personal data, or proprietary content, violating GDPR and other data protection regulations. Integrity of published articles or site content could be compromised, damaging organizational reputation. Availability impacts may arise if attackers execute destructive SQL commands or cause database errors. Given the remote exploitation capability without authentication, public-facing installations are particularly vulnerable. The medium severity suggests moderate risk, but the actual impact depends on the database privileges and the sensitivity of stored data. Organizations in sectors with strict compliance requirements or high-value data are at greater risk of regulatory penalties and operational disruptions.

Summary

CVE-2025-15014 identifies a SQL injection vulnerability in the php loganSite content management system developed by loganhong. The vulnerability resides in the /includes/article_detail.php file, specifically within the Article Handler component, where the 'ID' parameter is improperly sanitized or validated before being used in SQL queries. This flaw enables remote attackers to inject malicious SQL code by manipulating the 'ID' argument, potentially allowing unauthorized access to or modification of the underlying database. The vulnerability does not require authentication or user interaction, increasing its risk profile. The product uses a rolling release model, complicating version tracking and patch management. The CVSS 4.0 base score is 5.3 (medium severity), reflecting network attack vector, low attack complexity, no privileges or user interaction required, but limited impact on confidentiality, integrity, and availability. No public exploits or patches are currently available, and the affected commit is c035fb5c3edd0b2a5e32fd4051cbbc9e61a31426. Organizations deploying php loganSite should audit their installations for this commit and monitor for anomalous database queries. The vulnerability could be exploited to extract sensitive data, alter content, or disrupt service, depending on the database privileges of the web application.

References

Community reviews

Loading reviews…