CVE-2025-8223VulnerabilityPublished 27 Jul 2025Updated 28 Jul 2025

CVE-2025-8223: jerryshensjf JPACookieShop 蛋糕商城JPA版 · Cross-Site Request Forgery

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

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

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: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: 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-25.

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-8223 effectively, European organizations should implement multiple layers of defense: 1) Apply any available patches or updates from the vendor promptly once released. 2) If patches are unavailable, implement web application firewall (WAF) rules to detect and block suspicious CSRF attack patterns targeting the affected endpoints. 3) Enforce strict anti-CSRF tokens in all state-changing requests within the application, ensuring tokens are unique per session and validated server-side. 4) Require re-authentication or multi-factor authentication (MFA) for sensitive administrative actions to reduce risk from forged requests. 5) Employ Content Security Policy (CSP) headers to restrict the sources of executable scripts and reduce the risk of malicious script injection facilitating CSRF. 6) Conduct user awareness training to recognize phishing attempts that may deliver CSRF payloads. 7) Monitor logs for unusual administrative activity that could indicate exploitation attempts. 8) Consider isolating administrative interfaces behind VPNs or IP allowlists to limit exposure to external attackers.

Description

A vulnerability, which was classified as problematic, was found in jerryshensjf JPACookieShop 蛋糕商城JPA版 up to 24a15c02b4f75042c9f7f615a3fed2ec1cefb999. This affects an unknown part of the file AdminTypeCustController.java. The manipulation leads to cross-site request forgery. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. This product does not use versioning. This is why information about affected and unaffected releases are unavailable.

Impact

For European organizations using the JPACookieShop 蛋糕商城JPA版 platform, this vulnerability poses a moderate risk. An attacker could leverage CSRF to perform unauthorized administrative actions, potentially altering customer data, configurations, or other sensitive settings within the e-commerce platform. This could lead to data integrity issues, unauthorized transactions, or manipulation of business logic. Although the vulnerability does not directly compromise confidentiality or availability, the integrity impact could disrupt business operations and customer trust. Given that the product is an e-commerce platform, organizations relying on it for online sales could face reputational damage and financial loss if attackers exploit this vulnerability to manipulate orders or customer information. The lack of versioning and patches complicates timely remediation, increasing exposure duration. European organizations with web-facing administrative interfaces are particularly at risk, especially if they do not implement CSRF protections at the application or infrastructure level.

Summary

CVE-2025-8223 is a Cross-Site Request Forgery (CSRF) vulnerability identified in the jerryshensjf JPACookieShop 蛋糕商城JPA版 product, specifically affecting the AdminTypeCustController.java component. This vulnerability allows an attacker to trick an authenticated administrator or user into submitting unwanted requests to the web application without their consent. The vulnerability is remotely exploitable without requiring any privileges or authentication, and it requires user interaction (such as clicking a malicious link or visiting a crafted webpage). The CVSS 4.0 base score is 5.3 (medium severity), reflecting that the attack vector is network-based with low attack complexity and no privileges required, but user interaction is necessary. The impact primarily affects the integrity of the application, as the attacker can manipulate administrative functions or customer types via forged requests. Confidentiality and availability impacts are minimal or none. The product does not use versioning, making it difficult to determine the full scope of affected releases. No official patches or mitigations have been published yet, and while the exploit has been publicly disclosed, there are no known exploits actively used in the wild at this time.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 4 Aug 2025, 00:58 UTC

Technical details

References

Community reviews

Related threats