Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2013-5038: Authentication Bypass in HOT HOTBOX Router 2.1.11

Published Dec 30, 2013 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.8Medium · v2
EPSS3.3%89th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Hot
IdentifiersCVE-2013-5038CWE-287 · Improper Authentication

CVE-2013-5038 describes an authentication bypass vulnerability in the HOT HOTBOX router running software version 2.1.11. The vulnerability allows remote attackers to bypass authentication by configuring their source IP address to match one that was previously used for an authenticated session. The router's authentication mechanism fails to properly validate session state, relying instead on the source IP address as a trust anchor.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker can gain unauthorized access to the router's administrative interface or other protected resources by spoofing the source IP address of a previously authenticated session. This could allow for full compromise of the device, including configuration changes, network disruption, or further attacks on internal network resources.

Mitigation

If you can’t patch tonight, do this now.

Restrict access to the router's management interface to trusted networks only, and implement network-level controls (such as firewall rules) to prevent unauthorized access. Monitor for unusual access patterns or repeated source IP changes. Where possible, use VPN or other secure remote access methods to further limit exposure.

Remediation

Patch, then assume compromise.

Upgrade the router firmware to a version that properly tracks session state and does not rely solely on source IP address for authentication. If no patch is available, contact the vendor for support or consider replacing the device with a model that is not affected by this vulnerability.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
HotHotbox Routerhardware
HotHotbox Router Firmwareoperating_system
FAQ

Frequently asked questions

Is CVE-2013-5038 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2013-5038 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2013-5038?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2013-5038.
Is there a patch for CVE-2013-5038?
Upgrade the router firmware to a version that properly tracks session state and does not rely solely on source IP address for authentication. If no patch is available, contact the vendor for support or consider replacing the device with a model that is not affected by this vulnerability.
What products are affected by CVE-2013-5038?
Hotbox Router and Hotbox Router Firmware.
How severe is CVE-2013-5038?
CVE-2013-5038 has a CVSS v2 score of 5.8 (Medium) and an EPSS score of 3.3% (89th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.