How severe is CVE-2024-25735?

CVE-2024-25735 has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2024-25735?

Affected package information for CVE-2024-25735 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2024-25735?

No fixed version has been published for CVE-2024-25735 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2024-25735 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2024-25735, including 1 documented proof-of-concept exploit on Exploit-DB. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2024-25735?

CVE-2024-25735 has an EPSS (Exploit Prediction Scoring System) score of 90.4%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2024-25735?

CVE-2024-25735 is classified as CWE-319 (CWE-319). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2024-25735?

CVE-2024-25735 affects wyrestorm apollo vx20 firmware. Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2024-25735?

A Nuclei detection template exists for CVE-2024-25735, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2024-25735 published, and has it been updated?

CVE-2024-25735 was published on March 27, 2024 and was last updated on November 4, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2024-25735

CRITICAL

An issue was discovered on WyreStorm Apollo VX20 devices before 1.3.58. Remote attackers can discover cleartext passwords via a SoftAP /device/config GET request.

Published

Mar 27, 2024

Updated

Nov 4, 2025

Affected

0 pkgs

Patched

None yet

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

90.4%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

An issue was discovered on WyreStorm Apollo VX20 devices before 1.3.58. Remote attackers can discover cleartext passwords via a SoftAP /device/config GET request.

Affected Products

1 product · 1 configurations

apollo vx20 firmwarewyrestorm

< 1.3.58

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-51816remotemultiple

Wyrestorm Apollo VX20 < 1.3.58 - Incorrect Access Control 'Credentials Disclosure'

by hyp3rlinx · Feb 26, 2024

Exploit-DB Source

Frequently Asked Questions

An issue was discovered on WyreStorm Apollo VX20 devices before 1.3.58. Remote attackers can discover cleartext passwords via a SoftAP /device/config GET request.

O3 Security · Impact-Aware SCA

Is CVE-2024-25735 in your stack?

O3 detects CVE-2024-25735 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works