Categories
CVE-2025-53476 medium CVSS 5.3

Vulnerability in OpenPLC _v3 a931181e8b81e36fadf7b74d5cba99b73c3f6d58 (CVE-2025-53476)

Summary

Vulnerability in OpenPLC _v3 a931181e8b81e36fadf7b74d5cba99b73c3f6d58 (CVE-2025-53476). Risk of unauthorized operations or information disclosure.

Original description

The description as published by the source.

A denial of service vulnerability exists in the ModbusTCP server functionality of OpenPLC _v3 a931181e8b81e36fadf7b74d5cba99b73c3f6d58. A specially crafted series of network connections can lead to the server not processing subsequent Modbus requests. An attacker can open a series of TCP connections to trigger this vulnerability.

Source: NIST National Vulnerability Database NVD

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-53476 has been found in OpenPLC _v3 a931181e8b81e36fadf7b74d5cba99b73c3f6d58.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "OpenPLC _v3 a931181e8b81e36fadf7b74d5cba99b73c3f6d58 CVE-2025-53476" on the vendor's site.

CVE-2025-53476 (OpenPLC _v3 a931181e8b81e36fadf7b74d5cba99b73c3f6d58) — CWE-775 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-775) exists in OpenPLC _v3 a931181e8b81e36fadf7b74d5cba99b73c3f6d58.

📍 Affected scope

Check the vendor advisory for the affected versions of OpenPLC _v3 a931181e8b81e36fadf7b74d5cba99b73c3f6d58.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで OpenPLC _v3 a931181e8b81e36fadf7b74d5cba99b73c3f6d58 を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details