dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2023-7325

CRITICAL · 9.3 CVSS v4.0 Published 2025-10-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Anheng Mingyu Operation and Maintenance Audit and Risk Control System up to 2023-08-10 contains a server-side request forgery (SSRF) vulnerability in the xmlrpc.sock handler. The product accepts specially crafted XML-RPC requests that can be used to instruct the server to connect to internal unix socket RPC endpoints and perform privileged XML-RPC methods. An attacker able to send such requests can invoke administrative RPC methods via the unix socket interface to create arbitrary user accounts on the system, resulting in account creation and potential takeover of the bastion host. VulnCheck has observed this vulnerability being exploited in the wild as of 2025-10-30 at 00:30:17.837319 UTC.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Anheng Mingyu Operation and Maintenance Audit and Risk Control System contains an SSRF vulnerability in the xmlrpc.sock handler. Attackers can send specially crafted XML-RPC requests to instruct the server to connect to internal Unix socket RPC endpoints, bypassing normal access controls to invoke administrative RPC methods that create arbitrary user accounts, enabling full system compromise.

MitigationRestrict access to the xmlrpc.sock endpoint and implement strict authentication/authorization for all XML-RPC requests; apply network segmentation to prevent unauthorized access to internal Unix socket interfaces; deploy vendor patches when available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Anheng Mingyu Operation and Maintenance Audit and Risk Control System is installed
    Locate the application installation directory or check system services for the Mingyu system components; look for processes named 'mingyu', 'audit', or related binaries
    Affected if The system is running the Anheng Mingyu Operation and Maintenance Audit and Risk Control System
  2. Verify the xmlrpc.sock endpoint is accessible
    Check for the presence of xmlrpc.sock file in the application directory, typically found in runtime or var directories; attempt a local curl or netcat connection to the socket if it exists
    Affected if The xmlrpc.sock file exists and is readable by the web service user
  3. Confirm XML-RPC service is enabled and listening
    Review application configuration files for xmlrpc enable settings; check network listeners or unix socket bindings for xmlrpc-related services
    Affected if XML-RPC functionality is enabled in the configuration and the service is running
  4. Check network exposure of the xmlrpc interface
    Review firewall rules, reverse proxy configurations, or application access controls that may allow external access to the XML-RPC endpoint
    Affected if The xmlrpc.sock endpoint is reachable from untrusted networks without authentication
  5. Audit XML-RPC request handling for socket connection capabilities
    Examine XML-RPC request logs or packet captures to identify attempts to connect to internal unix sockets; check if the XML parser allows socket path parameters
    Affected if The XML-RPC handler processes requests containing socket path parameters without validation

A user is affected if they run the Anheng Mingyu system with the xmlrpc.sock endpoint exposed and XML-RPC service enabled, allowing external or untrusted access to internal socket communication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict access to the xmlrpc.sock endpoint and implement strict authentication/authorization for all XML-RPC requests; apply network segmentation to prevent unauthorized access to internal Unix socket interfaces; deploy vendor patches when available.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-7325 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-7325 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data