Security readout for executives and security teams
Plain-English summary
A remote, unauthenticated attacker can abuse the Mingyu management system to create administrator-capable accounts, potentially taking control of the bastion host and the systems it protects. The supplied sources report exploitation in the wild, making this an immediate operational risk where affected systems are reachable.
Executive priority
Treat exposed or potentially affected systems as an immediate incident-response and remediation priority. Assign ownership now, restrict access, hunt for unauthorized accounts, and obtain vendor-supported remediation. Because exploitation is reported and a successful attack may compromise a privileged bastion host, delayed action could expose downstream managed systems.
Technical view
The xmlrpc.sock handler permits SSRF into internal Unix-socket XML-RPC services without authentication. Crafted requests can reach privileged administrative methods and create arbitrary users. CVSS 4.0 is 9.3, with high confidentiality and integrity impact. The supplied version information is imprecise, but identifies systems through 10 August 2023 as affected.
Likely exposure
Highest risk applies to affected Mingyu appliances whose vulnerable XML-RPC handler is reachable from untrusted networks. Internal-only systems remain exposed to attackers with network access. The source bundle does not establish reliable fixed-version boundaries, deployment prevalence, or whether later releases are safe.
Exploitation context
VulnCheck reports observing exploitation in the wild on 30 October 2025. CVE-2023-7325 is not identified as CISA KEV in the supplied bundle. Public references are tagged as containing exploit information, increasing practical risk, although the bundle provides no campaign scope or attacker attribution.
Researcher notes
The weakness combines SSRF (CWE-918) with missing authentication for critical functionality (CWE-306). The stated outcome is privileged user creation through internal Unix-socket RPC methods. Precise affected versions, patch availability, indicators, and exploitation scale are not established by the supplied evidence and require vendor or additional authoritative confirmation.
Mitigation direction
- Identify every deployed Mingyu Operations and Maintenance Audit and Risk Control System instance.
- Immediately restrict appliance access to trusted management networks and authorized administrators.
- Remove direct internet exposure and apply network filtering around the XML-RPC interface.
- Check current vendor guidance for fixed versions or supported mitigations; none are named in the supplied sources.
- Investigate suspicious accounts and isolate potentially compromised appliances before restoring trusted administration.
Validation and detection
- Confirm product versions and deployment dates against authoritative vendor inventory and guidance.
- Test whether the XML-RPC handler is reachable from internet-facing or untrusted network segments.
- Review user-account records for unexpected, recently created, or newly privileged accounts.
- Examine appliance and network logs for anomalous XML-RPC requests and internal socket access.
- Verify compensating access controls from both permitted and untrusted network locations.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-7325 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://cn-sec.com/archives/1947658.htmlCVE reference, VulnCheck · exploit
- https://github.com/PeiQi0/PeiQi-WIKI-Book/blob/main/docs/wiki/iot/%E5%AE%89%E6%81%92/%E5%AE%89%E6%81%92%20%E6%98%8E%E5%BE%A1%E8%BF%90%E7%BB%B4%E5%AE%A1%E8%AE%A1%E4%B8%8E%E9%A3%8E%E9%99%A9%E6%8E%A7%E5%88%B6%E7%B3%BB%E7%BB%9F%20xmlrpc.sock%20%E4%BB%BB%E6%84%8F%E7%94%A8%E6%88%B7%E6%B7%BB%E5%8A%A0%E6%BC%8F%E6%B4%9E.mdCVE reference, VulnCheck · exploit
- https://www.vulncheck.com/advisories/mingyu-operations-and-maintenance-audit-and-risk-control-system-xmirpc-sock-ssrfCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.