CVE-2025-2851
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 · uneditedA vulnerability classified as critical has been 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. Affected is an unknown function of the file plugins.so of the component RPC Handler. The manipulation leads to buffer overflow. 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 · moderate confidenceA buffer overflow vulnerability exists in the plugins.so RPC Handler component of multiple GL.iNet router firmware 4.x versions (including GL-A1300, GL-AR750, GL-AX1800, GL-MT3000, and others). The overflow occurs during RPC request processing and could allow remote attackers to execute arbitrary code or cause denial of service.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the router modelAccess the router admin interface or check the device label to confirm it is a GL.iNet model (e.g., GL-A1300, GL-AR750, GL-AX1800, GL-MT3000).Affected if The device is a GL.iNet router from the affected product line.
-
Check the firmware versionIn the router admin panel, navigate to System > Overview or System > Firmware to view the installed firmware version. Compare it against the 4.x branch.Affected if The firmware version is in the 4.x branch.
-
Verify the plugins.so component existsAccess the router via SSH and check for the plugins.so file in the filesystem, typically located under /usr/lib or /lib directory. Use: find / -name plugins.so 2>/dev/nullAffected if The plugins.so library file is present on the device.
-
Confirm RPC service is enabledCheck the router configuration for RPC handler settings. In the admin interface, look under Application > Plugins or similar RPC-related settings. Alternatively, run: ps | grep rpc to see if an RPC process is running.Affected if The RPC service or plugin handler is actively running on the router.
-
Assess network exposure of the RPC interfaceCheck firewall rules and network configuration to determine if the RPC service is reachable from the WAN or untrusted networks. Review iptables rules or the firewall settings page.Affected if The RPC service is exposed to the WAN or untrusted network segments.
If the device is a GL.iNet router running firmware 4.x with the plugins.so component and RPC service enabled and network-accessible, the environment is likely affected by CVE-2025-2851.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedUpgrade the affected GL.iNet router firmware to the latest version that includes the patched plugins.so component. Review network exposure of RPC services and implement firewall rules to limit unauthorized access to management interfaces.
Latest 4.x firmware release from GL.iNet (specific version numbers not provided in vulnerability data)
- 1. Identify your specific GL.iNet router model from the affected list (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, or GL-XE3000)
- 2. Visit the official GL.iNet download page at https://www.gl-inet.com/downloads/
- 3. Locate the firmware download section for your specific router model
- 4. Download the latest stable firmware version available for your device
- 5. Access your router's web administration panel (typically at 192.168.8.1)
- 6. Navigate to the Firmware Upgrade or System Settings section
- 7. Upload and install the latest firmware file
- 8. After reboot, verify the upgrade was successful and confirm the new firmware version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2851 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-2851 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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