VulnerabilityPublished 27 Jul 2025Updated 28 Jul 2025

CVE-2025-8221: jerryshensjf JPACookieShop 蛋糕商城JPA版 · Cross-site Scripting

Affects jerryshensjf JPACookieShop 蛋糕商城JPA版Source CVE Database V5

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.5% chance of exploitation in 30 days – higher than 44% 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: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: None
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: 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: 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 27 Jul 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 this vulnerability, European organizations should: 1) Immediately review and sanitize all user inputs, especially the 'keyword' parameter in the goodsSearch function, employing context-appropriate output encoding to neutralize malicious scripts. 2) Implement Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. 3) Conduct thorough code audits focusing on input validation and output encoding across the application. 4) Monitor web application logs for unusual or suspicious requests targeting the goodsSearch endpoint. 5) Engage with the vendor or development team to obtain patches or updates addressing this vulnerability, considering the rolling release model may delay formal patch releases. 6) Educate users and administrators about the risks of XSS and encourage cautious handling of suspicious links or inputs. 7) Employ web application firewalls (WAFs) with rules tailored to detect and block XSS payloads targeting this specific parameter.

Description

A vulnerability classified as problematic was found in jerryshensjf JPACookieShop 蛋糕商城JPA版 up to 24a15c02b4f75042c9f7f615a3fed2ec1cefb999. Affected by this vulnerability is the function goodsSearch of the file GoodsCustController.java. The manipulation of the argument keyword leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available.

Impact

For European organizations using JPACookieShop 蛋糕商城JPA版, this XSS vulnerability poses a moderate risk. Successful exploitation could allow attackers to steal session cookies, impersonate users, or conduct phishing attacks by injecting malicious scripts into web pages viewed by legitimate users. This can lead to unauthorized access to user accounts, data leakage, and reputational damage. E-commerce platforms are particularly sensitive due to the handling of customer data and payment information. Even though the vulnerability does not directly compromise system availability or integrity, the indirect consequences such as loss of customer trust and potential regulatory penalties under GDPR for insufficient protection of personal data could be significant. The remote exploitability and lack of required privileges increase the attack surface, especially for organizations with public-facing instances of this software.

Summary

CVE-2025-8221 is a cross-site scripting (XSS) vulnerability identified in the JPACookieShop 蛋糕商城JPA版 application developed by jerryshensjf. The vulnerability exists in the goodsSearch function within the GoodsCustController.java file. Specifically, the issue arises from improper handling and sanitization of the 'keyword' parameter, which is susceptible to injection of malicious scripts. An attacker can remotely exploit this vulnerability by crafting a specially designed request that includes malicious JavaScript code in the keyword argument. When the application processes this input and renders it in the response without adequate encoding or sanitization, the malicious script executes in the context of the victim's browser. This can lead to session hijacking, defacement, or redirection to malicious sites. The vulnerability has been publicly disclosed, and while no confirmed exploits in the wild are reported, the availability of proof-of-concept code increases the risk of exploitation. The product uses a rolling release model, which complicates precise version tracking for affected and patched releases. The CVSS 4.0 base score is 5.3 (medium severity), reflecting the network attack vector, no privileges or authentication required, user interaction needed, and limited impact on confidentiality and integrity but no impact on availability.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 4 Aug 2025, 01:05 UTC

Technical details

References

Community reviews

Related threats