Skip to main content
CVE-2025-51663VulnerabilityPublished Updated

IPRateLimit implementation of FileCodeBox · CWE-305

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-51663· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 2.3 soon.

Data as of 13 Nov 2026, 19:31 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 2.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade vastsa/FileCodeBox to 2.3.

Affected software

ProductAffectedFixed in
GitHubvastsa/FileCodeBoxpkg:github/vastsa/FileCodeBoxOther threatsAffected
  • <2.3
Fixed in
  • 2.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, consider implementing additional protections such as validating or ignoring spoofed HTTP headers for IP rate limiting, or applying rate limiting based on other reliable identifiers.

Description

A vulnerability in the IPRateLimit implementation of FileCodeBox versions up to 2.2 allows remote attackers to bypass IP-based rate limiting and failed attempt restrictions by spoofing the X-Real-IP and X-Forwarded-For HTTP headers. This bypass can enable denial-of-service (DoS) attacks or brute force attempts on share codes.

References

Community reviews

Loading reviews…