VulnerabilityPublished 23 Feb 2026Updated 25 Feb 2026

CVE-2026-3041: xingfuggz BaykeShop · Cross-site Scripting

Affects xingfuggz BaykeShopSource CVE Database V5

Compare

Public exploit available · CVSS 4.8 Medium.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 4.0 base score

4.8Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/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: High
User Interaction: Passive
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: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
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 23 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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

Affected software

Product	Affected	Fixed in
xingfuggzBaykeShop	Affected 1.3.0 – 1.3.20 21 affected builds	Fixed in–
GitHubxingfuggz/baykeShop`pkg:github/xingfuggz/baykeShop`Other threats	Affected 1.3.0 – 1.3.20 21 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until an official patch is released, organizations should implement several specific mitigations: 1) Apply strict input validation and output encoding on the sidebar.content parameter to neutralize malicious scripts. 2) Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce XSS impact. 3) Use web application firewalls (WAFs) with custom rules to detect and block suspicious payloads targeting the vulnerable template. 4) Educate users and administrators about phishing risks and suspicious links to reduce successful user interaction exploitation. 5) Monitor web server logs and application behavior for unusual requests or error patterns indicative of exploitation attempts. 6) Isolate or disable the Article Sidebar Module if feasible to reduce the attack surface. 7) Regularly back up site data and configurations to enable recovery if compromise occurs. 8) Engage with the vendor or community for updates and patches, and plan for prompt application once available. These targeted measures go beyond generic advice by focusing on the specific vulnerable component and attack vector.

Description

A security vulnerability has been detected in xingfuggz BaykeShop up to 1.3.20. Impacted is an unknown function of the file src/baykeshop/contrib/article/templates/baykeshop/sidebar/custom.html of the component Article Sidebar Module. Such manipulation of the argument sidebar.content leads to cross site scripting. The attack can be executed remotely. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Impact

The primary impact of CVE-2026-3041 is the potential for attackers to execute arbitrary scripts within the browsers of users interacting with vulnerable BaykeShop sites. This can lead to theft of session cookies, enabling account takeover, phishing attacks, or distribution of malware. For e-commerce platforms, such compromises can erode customer trust, lead to financial fraud, and damage brand reputation. Although the vulnerability does not directly affect system integrity or availability, the confidentiality breach can have cascading effects, including unauthorized transactions or data leakage. Organizations worldwide using BaykeShop versions up to 1.3.20 are at risk, especially those with significant customer interaction on their sites. The absence of a patch and public exploit disclosure increases the likelihood of targeted attacks, particularly against high-value e-commerce operations. The medium severity rating indicates a moderate but actionable threat that should be addressed promptly to prevent exploitation.

Summary

CVE-2026-3041 identifies a cross-site scripting vulnerability in the BaykeShop e-commerce platform developed by xingfuggz, affecting all versions up to 1.3.20. The vulnerability resides in the Article Sidebar Module, specifically within the template file src/baykeshop/contrib/article/templates/baykeshop/sidebar/custom.html. The issue arises from improper sanitization or validation of the sidebar.content parameter, which is user-controllable. An attacker can craft malicious input that, when rendered by the vulnerable template, executes arbitrary JavaScript in the context of the victim's browser. This XSS flaw is remotely exploitable without requiring authentication but does require user interaction, such as clicking a malicious link or visiting a compromised page. The CVSS v4.0 score of 4.8 (medium severity) reflects the attack vector as network-based with low attack complexity, no privileges required, but user interaction necessary. The impact primarily affects confidentiality through potential session hijacking or data theft, with limited integrity or availability impact. No known exploits are currently observed in the wild, but public disclosure increases the risk of exploitation attempts. The lack of vendor response and patch availability necessitates immediate attention from administrators of affected BaykeShop installations.

References

Community reviews

Loading reviews…