dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2025-2811

MEDIUM · 5.7 CVSS v3.1 Published 2025-04-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was found in GL.iNet GL-A1300 Slate Plus, GL-AR300M16 Shadow, GL-AR300M Shadow, GL-AR750 Creta, GL-AR750S-EXT Slate, GL-AX1800 Flint, GL-AXT1800 Slate AX, GL-B1300 Convexa-B, GL-B3000 Marble, GL-BE3600 Slate 7, GL-E750, GL-E750V2 Mudi, GL-MT300N-V2 Mango, GL-MT1300 Beryl, GL-MT2500 Brume 2, GL-MT3000 Beryl AX, GL-MT6000 Flint 2, GL-SFT1200 Opal, GL-X300B Collie, GL-X750 Spitz, GL-X3000 Spitz AX, GL-XE300 Puli and GL-XE3000 Puli AX 4.x. It has been declared as problematic. This vulnerability affects unknown code of the component API. The manipulation leads to inefficient regular expression complexity. It is recommended to upgrade the affected component.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A Regular Expression Denial of Service (ReDoS) vulnerability exists in the API component of multiple GL.iNet router firmware versions 4.x. The manipulation of API parameters triggers inefficient regular expression complexity, potentially causing service degradation or denial through specially crafted requests that exploit the regex pattern matching.

MitigationUpgrade the affected GL.iNet router firmware (GL-A1300, GL-AR300M16, GL-AR300M, GL-AR750, GL-AR750S-EXT, GL-AX1800, GL-AXT1800, GL-B1300, GL-B3000, GL-BE3600, GL-E750, GL-E750V2, GL-MT300N-V2, GL-MT1300, GL-MT2500, GL-MT3000, GL-MT6000, GL-SFT1200, GL-X300B, GL-X750, GL-X3000, GL-XE300, GL-XE3000) to the latest version that addresses this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify your GL.iNet router model
    Check the device label or access the admin panel to determine the exact model number (e.g., GL-A1300, GL-MT3000, GL-X3000). Compare against the list of affected models provided in the CVE documentation.
    Affected if The router model matches one of the following: GL-A1300, GL-AR300M16, GL-AR300M, GL-AR750, GL-AR750S-EXT, GL-AX1800, GL-AXT1800, GL-B1300, GL-B3000, GL-BE3600, GL-E750, GL-E750V2, GL-MT300N-V2, GL-MT1300, GL-MT2500, GL-MT3000, GL-MT6000, GL-SFT1200, GL-X300B, GL-X750, GL-X3000, GL-XE300, GL-XE3000.
  2. Determine the installed firmware version
    Access the router admin interface (typically at 192.168.8.1), navigate to System > Firmware or System > Overview, and record the current firmware version number.
    Affected if The firmware version begins with 4.x (e.g., 4.0.0, 4.1.5, 4.3.0). Versions prior to 4.x or later point releases that include the fix are not affected.
  3. Verify the API component is accessible
    Check if the router API endpoint is reachable. This is typically accessible via HTTP/HTTPS requests to the router's IP address on common API paths (e.g., /api or /cgi-bin/api). Use a web browser or curl to test connectivity.
    Affected if The API endpoint responds to requests, indicating it is exposed and potentially exploitable.
  4. Review API parameter handling
    Examine API traffic using browser developer tools or network capture tools while interacting with the router admin panel. Look for API calls that accept user-supplied parameters.
    Affected if The API accepts parameters that could be manipulated with specially crafted input designed to trigger inefficient regex pattern matching.
  5. Check firmware release notes
    Visit the official GL.iNet support or download page for your specific router model and review recent firmware release notes for security updates addressing ReDoS or regex-related issues.
    Affected if The current firmware version predates the patch for CVE-2025-2811, or no security fix is documented in the release notes.

Your router is likely affected if it is one of the listed GL.iNet models running firmware version 4.x, the API component is accessible, and the installed firmware predates the security patch for this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the affected GL.iNet router firmware (GL-A1300, GL-AR300M16, GL-AR300M, GL-AR750, GL-AR750S-EXT, GL-AX1800, GL-AXT1800, GL-B1300, GL-B3000, GL-BE3600, GL-E750, GL-E750V2, GL-MT300N-V2, GL-MT1300, GL-MT2500, GL-MT3000, GL-MT6000, GL-SFT1200, GL-X300B, GL-X750, GL-X3000, GL-XE300, GL-XE3000) to the latest version that addresses this vulnerability.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2811 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-2811 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data