VulnerabilityPublished 11 Oct 2025Updated 14 Oct 2025

CVE-2025-11594: ywxbear PHP-Bookstore-Website-Example · Improper Validation of Specified Quantity in Input

Affects ywxbear PHP-Bookstore-Website-ExampleSource CVE Database V5

Public exploit available · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

6.9Medium

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

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

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

Base metrics

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

Threat metrics

Exploit Maturity: POC

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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within 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: None: There is no impact to availability within 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.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

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 or the CVSS exploit maturity 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-11594, organizations should implement strict server-side validation of all quantity inputs, ensuring that only valid, expected numeric values within acceptable ranges are processed. Input sanitization must be enforced to reject negative, zero, or excessively large quantities. Business logic should include checks to verify that requested quantities align with available inventory and order policies. Employing web application firewalls (WAFs) with custom rules to detect and block anomalous quantity parameters can provide an additional layer of defense. Regular code audits and penetration testing focused on input validation are recommended. Since no official patches are available, organizations should consider isolating or restricting access to affected components until fixes can be applied. Monitoring logs for unusual order patterns or quantity anomalies can help detect exploitation attempts early. Finally, engaging with the vendor or community for updates on patches or mitigations is advised due to the rolling release model.

Description

A vulnerability has been found in ywxbear PHP-Bookstore-Website-Example and PHP Basic BookStore Website up to 0e0b9f542f7a2d90a8d7f8c83caca69294e234e4. This issue affects some unknown processing of the file /index.php of the component Quantity Handler. Such manipulation leads to improper validation of specified quantity in input. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases.

Impact

For European organizations, especially those operating e-commerce platforms or using PHP-based bookstore solutions derived from or similar to the ywxbear PHP-Bookstore-Website-Example, this vulnerability could lead to manipulation of order quantities. This may result in financial losses due to incorrect billing or inventory errors, undermining customer trust and operational efficiency. While the vulnerability does not directly compromise confidentiality or availability, the integrity issues could cascade into broader business process failures or audit compliance problems. Organizations relying on automated inventory or order management systems are particularly at risk. The lack of authentication requirement and ease of remote exploitation increase the threat surface. Given the rolling release nature of the product, timely patching may be challenging, prolonging exposure. European companies with integrated supply chains or regulatory obligations around transaction accuracy must prioritize addressing this issue to avoid reputational and financial damage.

Summary

CVE-2025-11594 identifies a vulnerability in the ywxbear PHP-Bookstore-Website-Example, specifically within the Quantity Handler logic processed in /index.php. The vulnerability arises from improper validation of the specified quantity input, allowing attackers to remotely submit manipulated quantity values without requiring authentication or user interaction. This can lead to unintended behavior such as incorrect order quantities, inventory mismanagement, or potential bypass of business rules that rely on quantity validation. The product operates on a rolling release basis, which complicates version tracking and patching, and no official patches or version updates have been disclosed. The CVSS 4.0 vector (AV:N/AC:L/AT:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P) indicates network attack vector, low attack complexity, no privileges or user interaction needed, no confidentiality or availability impact, but low impact on integrity. Although no known exploits are currently in the wild, the public disclosure of the vulnerability increases the risk of exploitation. The vulnerability primarily threatens the integrity of order processing and inventory data, potentially leading to financial discrepancies or operational disruptions in affected deployments.

References

Community reviews

Loading reviews…