WGR-500: Use of Externally-Controlled Format String
CVE-2025-48826 is a high-severity use of externally-controlled format string vulnerability in WGR-500 from Planet, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected WGR-500 versions: v1.3411b190912. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 7.25% chance of exploitation within 30 days, which is in the top 5.57% of all scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of WGR-500 you run against the affected versions below, and install the vendor's latest release.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Planet | WGR-500 | v1.3411b190912 | Not stated |
| Planet | Wgr-500 Firmware | 1.3411b190912 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (cisco.com).
Official description
A format string vulnerability exists in the formPingCmd functionality of Planet WGR-500 v1.3411b190912. A specially crafted series of HTTP requests can lead to memory corruption. An attacker can send a series of HTTP requests to trigger this vulnerability.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Externally-Controlled Format String
The product uses a function that accepts a format string as an argument, but the format string originates from an external source.
How developers prevent this class of flaw
- Choose a language that is not subject to this flaw.
- Ensure that all format string functions are passed a static string which cannot be controlled by the user, and that the proper number of arguments are always sent to that function as well. If at all possible, use functions that do not support the %n operator in format strings.
- Run compilers and linkers with high warning levels, since they may detect incorrect usage.
More Use of Externally-Controlled Format String vulnerabilities (CWE-134)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Technical write-ups (may include proof of concept)
- talosintelligence.com/vulnerability_reports/TALOS-2025-2228Exploit, Third Party Advisory
Other references
Other vulnerabilities in WGR-500
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
Recent Use of Externally-Controlled Format String vulnerabilities
- 8.8 High severity
- 9.8 Critical severity
- 7.2 High severity
- 9.8 Critical severity
- 8.1 High severity
- 7.2 High severity
Spotted an error? Tell us.