Linksys RE6500/RE6250/RE6300/RE6350/RE7000/RE9000 setDeviceURL os command injection
Noroxi assessment
Priority: Monitor (action score 25/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 13.7% (FIRST EPSS); higher than 96.4% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A vulnerability classified as critical was found in Linksys RE6500, RE6250, RE6300, RE6350, RE7000 and RE9000 1.0.013.001/1.0.04.001/1.0.04.002/1.1.05.003/1.2.07.001. This vulnerability affects the function setDeviceURL of the file /goform/setDeviceURL. The manipulation of the argument DeviceURL leads to os command injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
- Published
- Jun 2, 2025
- Updated
- Jun 17, 2026
- EPSS
- 13.7% · 96th percentile
- CWE
- CWE-77
Report tools
Action score
25
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 4 / 30 · 13.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · VulDB
- 5.3
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linksys | re9000 firmware | cpe:2.3:o:linksys:re9000_firmware |
| linksys | re9000 | cpe:2.3:h:linksys:re9000 |
| linksys | re6250 firmware | cpe:2.3:o:linksys:re6250_firmware |
| linksys | re6250 | cpe:2.3:h:linksys:re6250 |
| linksys | re6300 firmware | cpe:2.3:o:linksys:re6300_firmware |
| linksys | re6300 | cpe:2.3:h:linksys:re6300 |
| linksys | re6350 firmware | cpe:2.3:o:linksys:re6350_firmware |
| linksys | re6350 | cpe:2.3:h:linksys:re6350 |
| linksys | re7000 firmware | cpe:2.3:o:linksys:re7000_firmware |
| linksys | re7000 | cpe:2.3:h:linksys:re7000 |
| linksys | re6500 firmware | cpe:2.3:o:linksys:re6500_firmware |
| linksys | re6500 | cpe:2.3:h:linksys:re6500 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linksys re6250 firmware1.0.04.001
- linksys re6300 firmware1.2.07.001
- linksys re6350 firmware1.0.04.001
- linksys re6500 firmware1.0.013.001
- linksys re7000 firmware1.1.05.003
- linksys re9000 firmware1.0.04.002
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulDB). Independent of NVD's CPE analysis and usually ahead of it.
Linksys RE6250
- 1.0.013.001, 1.0.04.001, 1.0.04.002, 1.1.05.003, 1.2.07.001affected
Linksys RE6300
- 1.0.013.001, 1.0.04.001, 1.0.04.002, 1.1.05.003, 1.2.07.001affected
Linksys RE6350
- 1.0.013.001, 1.0.04.001, 1.0.04.002, 1.1.05.003, 1.2.07.001affected
Linksys RE6500
- 1.0.013.001, 1.0.04.001, 1.0.04.002, 1.1.05.003, 1.2.07.001affected
Linksys RE7000
- 1.0.013.001, 1.0.04.001, 1.0.04.002, 1.1.05.003, 1.2.07.001affected
Linksys RE9000
- 1.0.013.001, 1.0.04.001, 1.0.04.002, 1.1.05.003, 1.2.07.001affected
Same product
linksys: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-5447Linksys RE6500/RE6250/RE6300/RE6350/RE7000/RE9000 ssid1MACFilter os command injection30Monitor
- CVE-2025-5438Linksys RE6500/RE6250/RE6300/RE6350/RE7000/RE9000 WPS command injection29Monitor
- CVE-2025-5446Linksys RE6500/RE6250/RE6300/RE6350/RE7000/RE9000 RP_checkCredentialsByBBS os command injection25Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-5439Jun 2, 2025 · Linksys RE6500/RE6250/RE6300/RE6350/RE7000/RE9000 verifyFacebookLike os command injection23Monitor
- ← EarlierCVE-2025-5440Jun 2, 2025 · Linksys RE6500/RE6250/RE6300/RE6350/RE7000/RE9000 NTP os command injection23Monitor
- Later →CVE-2025-5442Jun 2, 2025 · Linksys RE6500/RE6250/RE6300/RE6350/RE7000/RE9000 RP_pingGatewayByBBS os command injection25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- pjqwudi (VulDB User)reporter
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-54470 days apartLinksys RE6500/RE6250/RE6300/RE6350/RE7000/RE9000 ssid1MACFilter os command injection30Monitor
- CVE-2025-54420 days apartLinksys RE6500/RE6250/RE6300/RE6350/RE7000/RE9000 RP_pingGatewayByBBS os command injection25Monitor
- CVE-2025-54430 days apartLinksys RE6500/RE6250/RE6300/RE6350/RE7000/RE9000 wirelessAdvancedHidden os command injection25Monitor
- CVE-2025-54440 days apartLinksys RE6500/RE6250/RE6300/RE6350/RE7000/RE9000 RP_UpgradeFWByBBS os command injection25Monitor
- CVE-2025-54450 days apartLinksys RE6500/RE6250/RE6300/RE6350/RE7000/RE9000 RP_checkFWByBBS os command injection25Monitor
- CVE-2025-54460 days apartLinksys RE6500/RE6250/RE6300/RE6350/RE7000/RE9000 RP_checkCredentialsByBBS os command injection25Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-77 · Improper Neutralization of Special Elements used in a Command ('Command Injection')CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/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
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- LDAP InjectionCAPEC-136likelihood: High · High
- Command DelimitersCAPEC-15likelihood: High · High
- IMAP/SMTP Command InjectionCAPEC-183Medium
- Command InjectionCAPEC-248likelihood: Medium · High
- Manipulating Writeable Terminal DevicesCAPEC-40likelihood: High · Very High
- Exploiting Multiple Input Interpretation LayersCAPEC-43likelihood: Medium · High
- Manipulating Writeable Configuration FilesCAPEC-75likelihood: High · Very High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.