CVE-2025-8505VulnerabilityPublished 3 Aug 2025Updated 4 Aug 2025

CVE-2025-8505: 495300897 wx-shop · Cross-Site Request Forgery

Affects 495300897 wx-shopSource 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.2% chance of exploitation in 30 days – higher than 12% 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 3 Aug 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 this CSRF vulnerability, European organizations should implement several specific measures beyond generic advice: 1) Employ anti-CSRF tokens in all state-changing requests within wx-shop, ensuring that each request includes a unique, unpredictable token validated on the server side. 2) Enforce SameSite cookie attributes (preferably 'Strict' or 'Lax') to reduce the risk of cross-origin requests carrying authentication cookies. 3) Implement user interaction confirmation for sensitive actions, such as transaction approvals or account modifications, to reduce the risk of automated CSRF exploitation. 4) Monitor and restrict referrer headers and origin checks to validate legitimate requests. 5) Conduct thorough code reviews and security testing focusing on CSRF protections in the wx-shop codebase, especially given the rolling release nature. 6) Educate users and employees about the risks of clicking on suspicious links or visiting untrusted websites while authenticated. 7) If possible, isolate the wx-shop environment behind web application firewalls (WAFs) configured to detect and block CSRF attack patterns. 8) Engage with the vendor or community maintaining wx-shop to obtain patches or updates as soon as they become available and apply them promptly. 9) Consider temporary workarounds such as disabling certain functionalities or requiring re-authentication for critical operations until a fix is deployed.

Description

A vulnerability has been found in 495300897 wx-shop up to de1b66331368695779cfc6e4d11a64caddf8716e and classified as problematic. This vulnerability affects unknown code. The manipulation leads to cross-site request forgery. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available.

Impact

For European organizations using wx-shop, this vulnerability poses a moderate risk. Attackers could exploit CSRF to perform unauthorized actions on behalf of legitimate users, potentially leading to fraudulent transactions, unauthorized changes to user accounts, or manipulation of order data. This could result in financial losses, reputational damage, and regulatory compliance issues, especially under GDPR if personal data integrity is compromised. The medium severity score reflects that while the vulnerability does not directly expose sensitive data or cause system outages, it undermines trust in the application and could be a stepping stone for further attacks. Organizations relying on wx-shop for online sales or customer interactions should be aware that attackers might exploit this vulnerability via social engineering or malicious websites to target their customers or employees. The lack of patches and the rolling release model complicate timely remediation, increasing exposure time. Additionally, the public disclosure of the exploit details may lead to increased scanning and attack attempts targeting European deployments.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 11 Aug 2025, 01:01 UTC

Technical details

References

Community reviews

Related threats