CVE-2011-4501: The UPnP IGD implementation in Edimax EdiLinux on the Edimax BR-6104K with firmware before 3.25, Edimax 6114Wg, Canyon-Tech CN-WF512 with…
Noroxi assessment
Priority: Plan (action score 41/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: 4.2% (FIRST EPSS); higher than 91.1% of all records.
- No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Add it to your regular patch cycle. 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
The UPnP IGD implementation in Edimax EdiLinux on the Edimax BR-6104K with firmware before 3.25, Edimax 6114Wg, Canyon-Tech CN-WF512 with firmware 1.83, Canyon-Tech CN-WF514 with firmware 2.08, Sitecom WL-153 with firmware before 1.39, and Sweex LB000021 with firmware 3.15 allows remote attackers to establish arbitrary port mappings by sending a UPnP AddPortMapping action in a SOAP request to the WAN interface, related to an "external forwarding" vulnerability.
- Published
- Nov 22, 2011
- Updated
- Jun 16, 2026
- EPSS
- 4.2% · 91th percentile
- CWE
- CWE-16
Report tools
Action score
41
Add it to your regular patch cycle.
- CVSS
- 40 / 40 · 10.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.2%
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.
Is your version affected? Check itNoroxi 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 |
|---|---|---|
| edimax | br-6104k router firmware | cpe:2.3:o:edimax:br-6104k_router_firmware |
| edimax | br-6104k | cpe:2.3:h:edimax:br-6104k |
| edimax | 6114wg router firmware | cpe:2.3:o:edimax:6114wg_router_firmware |
| edimax | 6114wg | cpe:2.3:h:edimax:6114wg |
| canyon-tech | cn-wf512 router firmware | cpe:2.3:o:canyon-tech:cn-wf512_router_firmware |
| canyon-tech | cn-wf514 router firmware | cpe:2.3:o:canyon-tech:cn-wf514_router_firmware |
| canyon-tech | cn-wf512 | cpe:2.3:h:canyon-tech:cn-wf512 |
| canyon-tech | cn-wf514 | cpe:2.3:h:canyon-tech:cn-wf514 |
| sitecom | wl-153 router firmware | cpe:2.3:o:sitecom:wl-153_router_firmware |
| sitecom | wl-153 | cpe:2.3:h:sitecom:wl-153 |
| sweex | lb000021 router firmware | cpe:2.3:o:sweex:lb000021_router_firmware |
| sweex | lb000021 | cpe:2.3:h:sweex:lb000021 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canyon-tech cn-wf512all versions
- canyon-tech cn-wf512 router firmware1.83
- canyon-tech cn-wf514all versions
- canyon-tech cn-wf514 router firmware2.08
- edimax 6114wgall versions
- edimax 6114wg router firmware1.83
- edimax 6114wg router firmware2.08
- edimax br-6104kall versions
+6 more rows
- edimax br-6104k router firmware3.21
- sitecom wl-153all versions
- sitecom wl-153 router firmware1.31
- sitecom wl-153 router firmware1.34
- sweex lb000021all versions
- sweex lb000021 router firmware3.15
Same product
edimax: all recordsOther highest-scoring records for the same primary product.
- CVE-2011-4502The UPnP IGD implementation in Edimax EdiLinux on the Edimax BR-6104K with firmware before 3.25, Edimax 6114Wg, Canyon-Tech CN-WF512 with…42Plan
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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- C · data can be read
- Integrity
- C · data or configuration can be modified
- Availability
- C · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- C
- Integrity impact
- C
- Availability impact
- C
Weakness class (CWE)
CWE-16 · ConfigurationCVSS vector
AV:N/AC:L/Au:N/C:C/I:C/A:C
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.