Skip to main content
VulnerabilityPublished Updated

CVE-2025-57213: platform · Improper Access Control

Affects platformSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubfuyang_lipengjun/platformpkg:github/fuyang_lipengjun/platformOther threatsAffected
  • =1.0.0
Fixed in–

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

AI-suggested

Immediate mitigation should focus on implementing strict access control checks within the orderService.queryObject component to ensure only authorized users can access sensitive data. Organizations should conduct thorough code reviews and penetration testing targeting this component to identify and remediate access control weaknesses. Network-level controls such as web application firewalls (WAFs) can be configured to detect and block suspicious crafted requests targeting the vulnerable endpoint. Monitoring and logging of all access to the orderService.queryObject API should be enhanced to detect anomalous access patterns indicative of exploitation attempts. Until an official patch is released, consider applying temporary compensating controls such as IP whitelisting, rate limiting, or disabling the vulnerable functionality if feasible. Organizations should also prepare incident response plans specific to data exposure incidents and ensure compliance teams are ready to address potential GDPR notifications. Finally, maintain close communication with the platform vendor for timely patch releases and updates.

Description

Incorrect access control in the component orderService.queryObject of platform v1.0.0 allows attackers to access sensitive information via a crafted request.

References

Community reviews

Loading reviews…