I always see an ISP-provided router as a hazardous & untrusted device. If it offers bridged PPPoE, I would configure it so it works as a pure modem, even it means breaking into the telnet console. Otherwise, I would rather put my own router behind it, double-NAT and firewall it out of my own network.
In Germany, the Choice and Connection of Telecommunication Terminal Devices Act have been passed with the support of free and open source community, which ensure a user can use their own router to connect a broadband network.
The simplest of them have a webinterface. If that's leaky, there goes the whole thing because any website can try to connect to it.
I've seen many modems with a web interface, but it's often not routable to the public Internet in actual use, as the connection was bridged and the job of getting a public IP has been delegated to the PPPoE connection on the router behind it (You need to add another network interface, assign a IP address on your router inside the LAN segment under the control of the modem to reach it).
Some modems have a management link, it can be described as an universal ISP backdoor, only reachable in the ISP's LAN.
But in both cases, it's still better than a modem/router combined unit.
Maybe they went for offshort design/manufacturing, that's plausible since most box~ are now mediacenters so basically 80% like any internet tv box on ebay.
Don't know how custom the hardware is, but the firmware appears to be.
Lots of them were mitigated due to other bugs preventing you from actually reaching the code when you pass funny input, or the code turns out to be unused (random unused code in your binaries is a big code smell). It was functional: they clearly made sure it all worked. But if you would try to do anything outside of the happy flow, it would bug. The customer also had quite a fight over getting the source code (instead of binaries) in the first place.