Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious search.php?Search= link
-
DeliveryDeliver link to victim via phishing
-
ExploitVictim browser reflects unsanitized input
-
ExecutionInjected script executes in victim session
-
ImpactSteal session tokens or manipulate page
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the specific search feature in search.php to receive attacker-controlled input via the 'Search' argument, which is reflected into the page without sanitization. Being reflected XSS, the attack is NOT fully unattended: a victim must follow an attacker-supplied link or submit an attacker-controlled form (CVSS UI:P), so social engineering/phishing is the delivery prerequisite. No authentication is required of the attacker (PR:N), and default configurations are affected since the search function is core application functionality. Practical limits: impact is confined to the victim's browser session (integrity-only, VI:L), there is no server-side code execution, and real-world reach is bottlenecked by the product's near-zero deployment base. |
| Impact | This is a reflected cross-site scripting flaw (CWE-79) in the abandoned open-source Books4Cash PHP application, reported by VulDB. The provided CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N) scores 5.3 (medium) and indicates remote, unauthenticated, low-complexity attack but requiring passive user interaction (UI:P) and yielding only low integrity impact with no confidentiality or availability impact - consistent with a reflected XSS. Exploitation signals: publicly available exploit code exists (E:P / 'the exploit has been publicly disclosed'), but there is NO CISA KEV listing and NO EPSS score in the provided data, so there is no evidence of active or widespread exploitation. The strongest risk-dampening factor is real-world footprint: the vendor's own note that 'the code repository of the project has not been active for many years' plus the obscure dext34-morgan namespace indicate a hobby/retired project with negligible production deployment. Net: despite a public POC and a medium CVSS, this is a low real-world priority - the combination of required victim interaction, limited (integrity-only) impact, and a near-nonexistent install base outweighs the POC signal. No conflicting signals in the data, though the absence of EPSS/KEV should be read as 'not assessed/not listed,' not as confirmed safe. |
| Exploit ScenarioDerived | An attacker crafts a URL to search.php containing a malicious payload in the 'Search' parameter and lures an authenticated or anonymous user of a Books4Cash instance into clicking it. When the victim's browser loads the page, the unsanitized Search value is reflected into the response and the injected script executes in the victim's session context, enabling session/cookie theft or UI manipulation. A public proof-of-concept exploit for this reflected XSS has been disclosed. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 18, 2026
Reflected cross-site scripting (CWE-79) in the abandoned open-source PHP application Books4Cash allows unauthenticated remote attackers to inject arbitrary script into the search page by crafting a malicious 'Search' argument accepted by search.php. The payload is returned to the browser without sanitization, so the impact is confined to the victim's session - an attacker can execute script in the context of the site, deface or alter content, and potentially capture session data or perform actions as the victim. Exploitation is not unattended: a victim must follow an attacker-supplied link (CVSS UI:P social-engineering prerequisite), and publicly available exploit code exists per the CVSS 4.0 E:P metric and VulDB disclosure. Real-world exposure is limited because the project repository has been dormant for years and has a negligible deployment footprint; no CISA KEV entry indicates active exploitation.
RemediationAI
No vendor-released patch was identified at time of analysis, and none should be expected: the Books4Cash repository has been dormant for years and has no active maintainer issuing security fixes, so remediation must come from the deploying organization. The definitive fix is a source-level edit to search.php that HTML-entity-encodes the 'Search' argument before output - in PHP, wrap the reflected value with htmlspecialchars($value, ENT_QUOTES | ENT_SUBSTITUTE, 'UTF-8') (or htmlentities with the same flags) so that <, >, ", ' and & are neutralized; this is a small, low-risk patch that can be applied by forking the repository or hot-patching the deployed copy, and it does not alter search behavior for legitimate users. Where code changes are not possible, compensating controls in order of preference are: retire or replace the application, since an unmaintained codebase will accumulate further issues; disable or remove search.php entirely if the search feature is not business-critical (side effect: loss of search functionality, but the rest of the application continues to work); enforce a strict Content-Security-Policy header on all responses (e.g., script-src 'self' with no 'unsafe-inline') to block inline injected script, accepting that legacy inline JavaScript in the application would need to be moved to external files or allow-listed first; and deploy a WAF or reverse-proxy rule that rejects requests whose 'Search' parameter contains angle brackets, script keywords, or event-handler patterns (side effect: possible false positives on legitimate searches for literal HTML-like terms, and the rule must be tuned per parameter). Additional hardening includes setting HttpOnly and Secure flags on session cookies to limit the value of any successful script execution, and restricting access to the application to trusted networks while a permanent fix is arranged. Verification of any fix should include replaying the known proof-of-concept payload through the 'Search' parameter and confirming it is returned encoded.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Books4Cash is a small PHP web application (dext34-morgan/Books4Cash) whose search feature in search.php reads a user-supplied 'Search' argument and echoes it back into the HTML response without output encoding. CWE-79 (Improper Neutralization of Input During Web Page Generation, 'Cross-site Scripting') is the root cause class: the classic reflected-XSS pattern in which server-side templating concatenates request data directly into markup, so a URL such as search.php?Search=<script>...</script> executes in any browser that visits it. The assessed CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N confirms network-reachable, low-complexity exploitation with no attacker authentication (PR:N) but mandatory user interaction (UI:R), scope change (S:C) and limited confidentiality/integrity impact with no availability impact; the CVSS 4.0 vector adds AT:N and E:P, reflecting publicly known proof-of-concept code. There is no server-side code execution, SQL injection, or authentication bypass involved - the vulnerable surface is purely client-side script execution delivered through the reflected parameter. The wildcard CPE cpe:2.3:a:dext34-morgan:books4cash:*:*:*:*:*:*:*:* indicates no fixed version boundary exists in the identifier data, consistent with a project that has no maintained release stream.
Know when Books4Cash gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P
Remote, no auth and low complexity for a reflected XSS, but victim must click a crafted link (UI:R); script crosses into the browser context (S:C) with limited confidentiality/integrity impact and no availability impact.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
2DescriptionCVE.org
A vulnerability was determined in dext34-morgan Books4Cash up to a8d3e357db75c07ac5ffbadcbaee2aeb4db3e571. This affects an unknown part of the file search.php. Executing a manipulation of the argument Search can lead to cross site scripting. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized. The code repository of the project has not been active for many years.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
EUVD-2026-103388
GHSA-cg67-3c2h-6q2c
NVD
CVE.org
EPSS
VulDB
Exploit-DB