CVE-2025-45422
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 · uneditedIncorrect access control in Proximus b-box v8c.725A allows authenticated attackers to bypass normal restrictions and make arbitrary changes to port forwarding rules.
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 confidenceIncorrect access control in Proximus b-box v8c.725A router allows authenticated attackers to bypass normal authorization restrictions and make arbitrary changes to port forwarding rules. An attacker with valid credentials can modify port forwarding configurations beyond their intended permissions, potentially exposing internal services or enabling external access to sensitive systems.
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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
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 router model and firmware versionAccess the router admin interface (typically via web browser at 192.168.1.1) or check via diagnostic commands. Look for the device model (b-box v8c) and firmware version (725A) in the status or system information page.Affected if The router is a Proximus b-box v8c running firmware version 725A or earlier
-
Verify port forwarding feature is enabledNavigate to the router admin interface and locate the port forwarding or virtual server configuration section. Check if any port forwarding rules are defined or if the feature is accessible.Affected if Port forwarding configuration is accessible and rules can be defined or modified
-
Review existing port forwarding rulesIn the router admin interface port forwarding section, inspect all configured rules. Note the source IP, external port, internal IP, and internal port for each rule.Affected if Any port forwarding rule exists that was not authorized or that exposes unexpected internal services
-
Check user account privilegesIn the router admin interface user management or account settings, examine all defined user accounts and their assigned privilege levels. Verify if there are multiple accounts with different permission tiers.Affected if Multiple user accounts exist and the privilege separation for port forwarding is not properly enforced
A user is affected if they operate a Proximus b-box v8c router on firmware 725A or earlier and the port forwarding feature is accessible to authenticated users beyond their intended permission scope.
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.
From vendor dataApply vendor firmware updates when available; if no patch exists, consider network segmentation, restricting administrative access to trusted networks only, or replacing the affected device.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-45422 — 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-45422 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