CVE Tools
Back to CVE-2023-5388

How to verify CVE-2023-5388

Confirm whether your systems are actually affected — run the exact detection check below (Nuclei command or OpenVAS NVT). Detection only; it does not exploit.

Verify with OpenVAS

Greenbone/OpenVAS ships 76 NVT checks for CVE-2023-5388. OpenVAS detects this CVE by NVT OID — enable the NVT in your scan config, or confirm it is in your feed with the query below.

Confirm the NVT is in your feed (GMP)
gvm-cli socket --xml "<get_nvts nvt_oid='1.3.6.1.4.1.25623.1.0.127731' details='1'/>"
NVT OIDs (76)
  • 1.3.6.1.4.1.25623.1.0.127731since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.152190since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.152813since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.153661since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.171527since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.832882since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.832883since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.832884since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.832885since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.832886since 2026-06-25

+ 66 more NVTs

Confirmed exposed? That's one CVE on one host.
We check your whole external estate — hundreds of IPs and domains — for this and thousands more, on a schedule.
Scan my estate