CVE-2025-60784VulnerabilityPublished 5 Nov 2025

CVE-2025-60784: n/a

Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.5Medium

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

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Nov 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-60784, organizations should implement strict server-side validation and authorization checks for all input parameters, especially 'zhekou' and 'zid' in the /topfirst.php Pay module. Specifically: 1) Enforce whitelist validation on the 'zhekou' parameter to ensure discount values fall within acceptable, predefined ranges. 2) Authenticate and authorize the 'zid' parameter to confirm that the user initiating the transaction has permission to act on the specified user ID. 3) Implement logging and monitoring of discount-related transactions to detect anomalous patterns indicative of exploitation attempts. 4) Apply the principle of least privilege to user accounts to reduce the risk of exploitation by low-privilege attackers. 5) Conduct code reviews and penetration testing focused on input validation and access control mechanisms within the payment and voting modules. 6) If possible, deploy web application firewalls (WAFs) with custom rules to detect and block suspicious POST requests manipulating these parameters. 7) Engage with the vendor or development team to obtain patches or updates addressing this vulnerability. 8) Educate relevant staff about the risks of parameter manipulation and encourage prompt reporting of suspicious activities. These measures go beyond generic advice by focusing on parameter-specific controls and monitoring tailored to this vulnerability.

Description

CVE-2025-60784 is a medium-severity vulnerability in the XiaozhangBang Voluntary Like System V8.8 that allows remote attackers to manipulate the discount parameter (zhekou) in the /topfirst.php Pay module. By sending crafted HTTP POST requests with abnormally low discount values, attackers can purchase votes at reduced costs, causing economic loss. Additionally, modifying the zid parameter enables attackers to influence purchases on behalf of other users, amplifying the impact. The root cause is insufficient server-side validation of these parameters, leading to unauthorized discount manipulation and vote count tampering. Exploitation requires low privileges but no user interaction and can be performed remotely over the network. No known exploits are currently reported in the wild. This vulnerability primarily impacts the integrity of the voting system and may cause financial damage to operators. European organizations using this system or similar voting/payment modules should prioritize patching and implement strict server-side input validation to mitigate risks.

Impact

For European organizations utilizing the XiaozhangBang Voluntary Like System or similar voting/payment platforms, this vulnerability poses significant risks. The primary impact is economic loss due to unauthorized discounts on vote purchases, which can distort voting outcomes and damage the credibility of online voting or promotional campaigns. Organizations relying on such systems for marketing, customer engagement, or decision-making may face reputational damage if vote manipulation is detected. Additionally, the ability to influence purchases on behalf of other users raises concerns about fraud and potential legal liabilities under European consumer protection laws. The integrity of the voting data is compromised, which can affect business decisions and stakeholder trust. While availability and confidentiality are not directly impacted, the economic and reputational consequences can be severe. Given the medium severity and the requirement for some privileges, insider threats or compromised accounts could exploit this vulnerability. European entities in sectors such as e-commerce, digital marketing, and online community platforms are particularly at risk.

Summary

CVE-2025-60784 identifies a vulnerability in the XiaozhangBang Voluntary Like System version 8.8, specifically within the /topfirst.php Pay module. The vulnerability arises from inadequate server-side validation of two critical parameters: 'zhekou' (discount) and 'zid' (user identifier). An attacker can remotely send a crafted HTTP POST request with the 'zhekou' parameter set to an abnormally low value, thereby purchasing votes at a significantly reduced cost. This manipulation directly impacts the economic model of the voting system by allowing unauthorized discounts. Furthermore, by altering the 'zid' parameter, attackers can affect transactions on behalf of other users, potentially causing unfair vote inflation or economic loss to legitimate users. The vulnerability is classified under CWE-284 (Improper Access Control) and CWE-285 (Improper Authorization), indicating that the system fails to enforce proper authorization checks on these parameters. The CVSS v3.1 base score is 6.5 (medium severity), with an attack vector of network (AV:N), low attack complexity (AC:L), requiring privileges (PR:L), no user interaction (UI:N), unchanged scope (S:U), no confidentiality impact (C:N), high integrity impact (I:H), and no availability impact (A:N). This means an attacker with some level of privileges can exploit the vulnerability remotely without user interaction, compromising the integrity of the system by unauthorized discount manipulation and vote tampering. No patches or known exploits are currently available, emphasizing the need for proactive mitigation. The vulnerability can lead to economic loss for operators and undermine the trustworthiness of the voting system.

CWE-284Improper Access Control (opens in a new tab)
Pillar weaknessCWE Top 25 (2025): #19OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Embedding Scripts within Scripts (opens in a new tab)
Modification of Windows Service Configuration (opens in a new tab)
Malicious Root Certificate (opens in a new tab)
Intent Spoof (opens in a new tab)
WebView Exposure (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-285Improper Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that you perform access control checks related to your business logic. These checks may be different than the access control checks that you apply to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Cross Zone Scripting (opens in a new tab)
Directory Indexing (opens in a new tab)
Subverting Environment Variable Values (opens in a new tab)
Using Malicious Files (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 12 Nov 2025, 21:32 UTC

WeaknessesCWE-284, CWE-285

Technical details

References

Community reviews

Related threats