# Six critical CVEs in 26 hours: Oray routers and an open YesWiki

> Five flaws in the Oray Pugongying X5 Pro router and one in YesWiki add up to six critical CVEs in 26 hours. Two reach 9.9 and Oray does not respond to the notice.
> By José Maldonado · Cybersecurity · 2026-10-28

Six critical CVEs in 26 hours and not a single vendor patch for five of them. The records came to light between the afternoon of Sunday, October 25 and the morning of Monday, October 26, 2026, and the split is as uneven as it is revealing: five point to the same router, the Oray Pugongying X5 Pro in its 7.6.1 version, and the sixth exposes a YesWiki wiki that responds to anyone without asking for credentials.

The Oray-YesWiki pairing of this day shares neither sector nor distribution model, and yet it repeats the same underlying pattern. The five in the router are CRLF injections: someone inserts a line break inside a value that ends up written to a configuration file or a command line, and the device interprets what follows as a new order. Two notices reach 9.9 out of 10 and the other three stay at 9.1, all with a proof-of-concept exploit already published.

The detail that changes the conversation is privilege. The two highest-scoring notes require a low-privilege user session and the remaining three require administrator access, so no anonymous attacker executes commands outright. In YesWiki the opposite happens: a single GET without credentials is enough to read the password hashes from the database and to leave the server without threads with a SLEEP() call. The router vendor stays silent while the wiki already has a fixed version.

## Five values that end up in the device configuration

The five notices share a shape and differ in the place where the line break does damage. The pattern repeats: the program trusts a string that someone writes from the management console and pastes it without parsing into a file or a system call.

CVE

Component

Manipulated argument

CVSS v3.1

Access required

CVE-2026-116231

Ser2net

\`regmsg\`

9,9

user with session

CVE-2026-116232

SNMP

\`info.community\`

9,9

user with session

CVE-2026-116233

Dnsmasq

\`rent\_time\`

9,1

administrator

CVE-2026-116234

IPsec policy

\`secproto\`

9,1

administrator

CVE-2026-116235

L2TP authentication

\`Username\`

9,1

administrator

CVE-2026-116207

YesWiki Bazar

\`query\` field

9,1

none

None of the five Oray records includes a fixed version or a note about the published fix, and the product sheet still points to 7.6.1 as the only affected version in the range.

Ser2net exposes a serial port over the network and its \`regmsg\` parameter is the text sent when the connection is opened. The proof-of-concept exploit shows that a line break inside that banner allows existing files on the device to be overwritten, because the text ends up being read as one more directive, as confirmed by [CVE-2026-116231](https://www.cve.org/CVERecord?id=CVE-2026-116231)The same trick works with the SNMP community string, the string that acts as the read-write password: with a line break inside it, the daemon ends up executing commands as root, the result documented in [CVE-2026-116232](https://www.cve.org/CVERecord?id=CVE-2026-116232).

The other three reach the same root through less conspicuous paths. Dnsmasq receives the DHCP lease time in \`rent\_time\` and writes it to its configuration, so the injected value adds options to the service that hands out addresses on the local network. The \`secproto\` of the IPsec policy and the \`Username\` of L2TP end up in \`/etc/ipsec.conf\` and in VPN authentication, and the two published exploits refer to code execution as root.

## When 9.9 is not worse than 9.1

The difference between the five advisories is not in the impact, which in all of them touches confidentiality, integrity and availability, but in who can reach the parameter. The two 9.9-rated notes require an authenticated user, even a low-privilege one, whereas the three 9.1-rated ones require an administrator session. None is triggered from the internet without prior credentials, and all five involve a scope change, that factor that raises the score because the flaw compromises more than just the program itself.

The real risk is measured by the exposed administration surface. A panel accessible from outside the local network turns a 9.1 into an urgent matter, while one closed to the internal network remains a maintenance task.

As of this Monday, no confirmed exploitation of any of the five has been recorded, nor have they been added to the catalog of exploited vulnerabilities maintained by the US cybersecurity agency. The manufacturer received the notice before publication and did not respond, and there is also no patch or interim mitigation for the affected version.

## YesWiki, the flaw that does not require credentials

The sixth CVE comes from another world and with a different kind of urgency. The public Bazar entry search API accepts the \`query\` and \`searchfields\` parameters to name the fields to be searched. That name travels unvalidated into an alias between backticks in the SQL query, and the only filter applied is \`mysqli\_real\_escape\_string\`, a function intended for text literals that escapes quotes and backslashes but not the backtick, the character MySQL uses to open and close identifiers.

With a single unauthenticated GET request, a field name containing that backtick closes the alias and injects a subquery. The project's advisory describes full database reads, with password hashes among the reachable data, and thread exhaustion via \`SLEEP()\`, as reported by [CVE-2026-116207](https://www.cve.org/CVERecord?id=CVE-2026-116207)The 9.1 score accurately captures the scope: high confidentiality and availability, zero integrity, because the injection reads and blocks but does not write.

A dump of hashes opens the door to dictionary attacks against accounts that people reuse on other services, and that lesson has already been seen in the [a review of Ledger's security failures and the leaks surrounding them](https://observatorioblockchain.com/en/cybersecurity/que-falla-seguridad-ledger-implantes-espia-filtraciones/). Rotating passwords and closing open sessions is the first move.

The registry entry has a curious detail worth examining before running anything. The project's advisory has been published since October 9 and the corrected version, 4.7.0 or alpha4 of the 5.0 branch, has existed since that date; the CVE arrived on Sunday the 25th. The ranges do not fully match either, because the advisory starts at 4.6.7 and the registry at 4.6.0, so it is best to take the broader list, the one published by [GHSA-ccp2-6q93-hggh](https://github.com/YesWiki/yeswiki/security/advisories/GHSA-ccp2-6q93-hggh).

## What can an administrator do without a patch?

For Oray's five, there is no documented mitigation, and the advisory acknowledges that no countermeasures are listed, with replacing the device as the suggested way out. What remains is to reduce exposure by hand and assume the firmware will not change this week.

*   Locate any X5 Pro on version 7.6.1 and check whether its administration panel responds from outside the local network.
*   Shut down services nobody uses, especially SNMP, L2TP, the IPsec policy and the port that exposes Ser2net.
*   Move the device to a separate management network and remove the console from any path reachable from the internet.
*   Review the logs for new directives in \`/etc/ipsec.conf\`, altered SNMP communities or DHCP leases with options nobody configured.

In YesWiki the path is shorter and duller. Updating to 4.7.0, or to alpha4 if anyone lives on the 5.0 branch, closes the injection, and restricting anonymous access to the Bazar API while the deployment is prepared narrows the exposure window.

## The router nobody is going to patch this week

The scene repeats every few weeks in the cheap end of networking hardware: a critical flaw, a public exploit and a vendor that does not answer the analyst, as happened with [the two flaws in Broadcom's proprietary Wi-Fi that went unpatched across much of the installed base](https://observatorioblockchain.com/en/cybersecurity/broadcom-wifi-fallo-routers-sin-parche/), where the 2018 fix covered only part of the problem.

The Oray YesWiki case leaves the same question on the table, with one fundamental difference between the two halves. The wiki is open source software, has a patched version and its community patches within days, so the flaw expires for anyone who updates. The router is a closed box that only changes when the manufacturer releases firmware, and this time it has released nothing, so the customer's decision is not when to patch but how much longer that device is left in charge of their network.
