ViWeb Security Briefings
Short, source-based guidance on website and hosting security issues that matter to business website owners.
Scope and update schedule
Curated website and hosting security guidance drawn from public advisories and vendor records within ViWeb's service scope. Entries are general guidance, not a diagnosis of any particular site, and they do not provide complete or real-time coverage.
ViWeb researches daily at 10:00 Vietnam time. Entries are published when a useful, verified change exists, so daily research does not mean daily publication. Each entry shows the absolute date it was last verified. Check the original advisories before acting.
Page 3 of 5
- Attention Exploitation not established
Subscribe2 10.50 stops forged one-click unsubscribe links
Identifiers: Subscribe2-10.50-security-release
Subscribe2
Subscribe2 10.50, released 16 November 2026, fixes a weakness in the one-click unsubscribe link that the plugin inserts into notification emails through its unsubscribe tag. Those links could be forged, so anyone who knew a public subscriber's email address could remove that person from the list. Each link now carries a secret key and is only honoured when the key matches. The same release also fixes a bug where notification emails sent individually gave every recipient after the first the first recipient's unsubscribe link.
Who is affected: WordPress sites running Subscribe2 with public subscribers whose notification emails use the one-click unsubscribe tag match the vendor's description. The changelog does not describe the effect on other subscription workflows, so their exposure is unknown. The vendor does not state which earlier versions are affected.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
Simple Cloudflare Turnstile 1.44.6 closes two login bot-check gaps
Identifiers: Simple-Cloudflare-Turnstile-1.44.6-security-release
Simple Cloudflare Turnstile
On 16 November 2026 the Simple CAPTCHA with Cloudflare Turnstile plugin released version 1.44.6 with two security fixes listed in its changelog. When the "Only enable on default wp-login.php page" option was switched on, the Turnstile check on the WordPress login and registration forms could be skipped by writing the wp-login.php address differently. Separately, when "WordPress Login" and "WooCommerce Login" were both enabled together with that same option, the WooCommerce login form was not checked at all.
Who is affected: Only sites running this plugin with "Only enable on default wp-login.php page" enabled and Turnstile active on the WordPress login or registration forms, or on both WordPress and WooCommerce login, match the vendor's description. Sites that leave that option off, or that do not protect login forms, are not described as affected. The vendor does not state which earlier versions contain the issue, so no affected range can be assumed.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
Joplin Server 3.7.6 changelog lists four security hardening changes
Identifiers: Joplin-Server-3.7.6-security-release · GHSA-2j3q-h77f-c3pp · GHSA-hh9f-h7x6-m8m3
Joplin Server
The Joplin Server changelog records server-v3.7.6 as released on 16 November 2026 with four security entries. Commit c934c17 stops returning the message of unexpected errors, such as database errors, to clients and escapes request text in logged error messages. Commit 4360b81 only accepts a delta limit from 1 to 1000. Commit e454395 limits the user listing to non-sensitive fields. Commit 926f9bf sends at most one alert per hour when recovery codes are viewed. No CVE is attached to these changes.
Who is affected: This applies only to self-hosted Joplin Server. Joplin desktop and mobile apps and Joplin Cloud are not the subject of this changelog. The changelog does not say which versions introduced each weakness, so do not treat every older server or every client as affected. Separately, two advisories published on 16 November 2026, GHSA-2j3q-h77f-c3pp on API password changes not revoking sessions and GHSA-hh9f-h7x6-m8m3 on recovery code regeneration without re-authentication, were tested only on 3.7.3 and 3.7.2 respectively and list no verified fixed version. The second requires MFA to be enabled and a stolen valid session, and the account password is still needed to log in with a regenerated code, so it is not passwordless initial access. The alert throttle in 3.7.6 is a different change and does not by itself establish a fix for either advisory; whether 3.7.6 covers them is not stated in any reviewed source.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
MariaDB Community Server 16 November 2026 releases fix thirteen CVEs
Identifiers: CVE-2026-101802 · CVE-2026-101796 · CVE-2026-101794 · CVE-2026-101775 · CVE-2026-101747 · CVE-2026-101725 · CVE-2026-101679 · CVE-2026-101619 · CVE-2026-101618 · CVE-2026-101617 · CVE-2026-101615 · CVE-2026-101614 · CVE-2026-101608
MariaDB Community Server
On 16 November 2026 MariaDB published Community Server 12.3.4, 11.8.10, 11.4.14 and 10.11.20. The release notes list fixes for thirteen CVEs: CVE-2026-101802, CVE-2026-101796, CVE-2026-101794, CVE-2026-101775, CVE-2026-101747, CVE-2026-101725, CVE-2026-101679, CVE-2026-101619, CVE-2026-101618, CVE-2026-101617, CVE-2026-101615, CVE-2026-101614 and CVE-2026-101608. The vendor catalog shows a CVE publication date of 20 October 2026 for all of them, which is a record date rather than a sign of brand-new discoveries.
Who is affected: This concerns self-hosted MariaDB Community Server on the 12.3, 11.8, 11.4 and 10.11 branches. The catalog only states the fixed versions, so we cannot say every earlier build is affected. Oracle MySQL, MariaDB Enterprise Server and client libraries are separate products with their own advisories. Linux distribution packages often carry backported fixes under different version numbers, so check your distribution's security notes before judging a server out of date.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation reported
LatePoint booking plugin: customer account takeover via password reset (CVE-2026-118066)
Identifiers: CVE-2026-118066
LatePoint appointment booking plugin for WordPress
Wordfence published CVE-2026-118066 on 6 November 2026 for the LatePoint WordPress plugin, slug latepoint, versions 5.7.6 and earlier. The fix is 5.7.7, dated 2 November in the vendor changelog as security hardening credited to Wordfence. The current release 5.7.8, dated 3 November, contains further security changes; the vendor does not say they address this CVE. The vendor fix dates precede the 6 November advisory. The flaw is in how the public customer password reset handles its reset token.
Who is affected: Sites running the latepoint plugin at 5.7.6 or earlier with the public customer password reset reachable. The attack needs a matching customer record whose stored reset token is non-NULL within a valid 15-minute reset window. An attacker can initiate that window, so no prior reset request by the victim is required.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
Auth Armor Passwordless Login 1.0.3 and earlier: unauthenticated administrator takeover, no verified fix as of 16 November 2026 (CVE-2026-110960)
Identifiers: CVE-2026-110960
Auth Armor – Passwordless Login
CVE-2026-110960 affects the Auth Armor Passwordless Login WordPress plugin through version 1.0.3. Several plugin handlers are available to logged-out visitors without any authentication check. These handlers expose the site's stored Auth Armor API credentials and let an unauthenticated attacker reset an administrator's enrollment, then take over that administrator account. As of 16 November 2026, the WPScan and Patchstack notices list no fixed version, and the vendor readme shows a stable tag of 1.0.2 with a changelog entry for 1.0.3.
Who is affected: Any WordPress site with Auth Armor Passwordless Login installed at version 1.0.3 or earlier and the plugin's public handlers reachable is affected. As of 16 November 2026, no fixed version for this issue has been verified in the sources reviewed.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
Lazy Blocks (Custom Block Builder) before 3.0.0: unauthenticated code execution through REST routes (CVE-2026-127048)
Identifiers: CVE-2026-127048
Lazy Blocks / Custom Block Builder
CVE-2026-127048 affects the Lazy Blocks WordPress plugin, also listed as Custom Block Builder, in versions before 3.0.0. The plugin's REST permission checks return a value that WordPress treats as approval instead of a denial, so visitors with no account can reach routes that execute PHP code on the server. The flaw is fixed in version 3.0.0. That version dates back to 2022, so this is a newly published advisory about an old fix, not a new vendor release. Checked 16 November 2026.
Who is affected: Only WordPress sites running Lazy Blocks below 3.0.0 with the plugin's REST routes reachable are affected. Sites already on 3.0.0 or any later supported release are not affected by this specific issue. Separate fixes in later 4.x releases address different problems and do not change this version boundary.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
Cloud Storage Manager for Fluent Forms 1.2.0 and earlier: unauthenticated file write via Google Drive filename path traversal (CVE-2026-120522)
Identifiers: CVE-2026-120522
Cloud Storage Manager for Fluent Forms
On 14 November 2026 Wordfence disclosed CVE-2026-120522 in Cloud Storage Manager for Fluent Forms. In 1.2.0 and earlier, a REST route lacks an authorization check. An unauthenticated attacker can store their own Google Drive credentials in the plugin and trigger a download from a Drive they control. The filename returned by the provider is not confined to the intended downloads folder, so a crafted name can place a file elsewhere on the server. Remote code execution follows only if a PHP file lands in a web-accessible, executable location. Fixed in 1.2.5; the vendor's current release is 1.2.9.
Who is affected: Sites with Cloud Storage Manager for Fluent Forms active at 1.2.0 or earlier. Per the researcher, having Google Drive already connected is not a prerequisite. Server file permissions and PHP execution limits in upload directories change the severity but have not been verified as protection.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
HestiaCP 1.10.7 security release hardens root symlink handling, API authentication and password files
Identifiers: HestiaCP-1.10.7-security-release
HestiaCP
HestiaCP 1.10.7, published on 13 November 2026, is a release that carries a Security section. The notes describe fixing root following symlinks inside user home directories across web and mail domain scripts, rebuilds and domain moves, SSH key scripts, user backup and restore, and restic restores, which now land in a root-only staging directory. They also describe hardened API authentication, stricter handling of password, hash and temporary files, and protection of ROOT_USER SSH keys in the same way as access keys. Several items cite GHSA references that overlap earlier advisory events, so this is new release hardening rather than a new CVE event.
Who is affected: Relevant if your website sits on a server managed by HestiaCP, especially where several users share the panel, API access is enabled, or backups and restic restores run as root. If you only rent a site, your hosting administrator is the person who acts. The release targets the HestiaCP panel and also changes some bundled dependencies, such as Zlib, the webmail clients and the MariaDB target version. It does not promise coverage of independently packaged runtimes, databases or applications, so those need their own check. Whether the release has been installed or activated depends on how each hosting setup handles updates, so confirm rather than assume.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
Nuxt 4.6.4: leading double slash bypasses server middleware and route rules on page routes
Identifiers: CVE-2026-128077 · GHSA-r99w-jh2x-3mg9
Nuxt @nuxt/nitro-server
GHSA-r99w-jh2x-3mg9 (CVE-2026-128077) is an incomplete fix for GHSA-9v7c-q64q-vv33. Since Nuxt 4.6.0, a request path that starts with `//` is parsed as a URL with a host before a page is rendered, so the page router resolves it to an ordinary page while Nitro routing, route rules and `server/middleware` see the raw path. The 4.6.3 fix covered dot segments only. The maintainers published the advisory and the fixed release on 2 November 2026; the advisory entered the reviewed GitHub Advisory Database on 13 November 2026.
Who is affected: Affected: `@nuxt/nitro-server` 4.6.0 to 4.6.3, which Nuxt 4.6.0 to 4.6.3 depends on. Not affected: handlers in `server/api` and `server/routes`, which Nitro does not match for these paths; `appMiddleware` route rules and middleware declared with `definePageMeta`, which match the resolved route; Nuxt 3.x and Nuxt 4.0.0 to 4.5.x, which pass the path unchanged and return 404. Other Nuxt 3 end-of-life findings are separate from this issue.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25 fix 52 security issues; PostgreSQL 14 reaches end of life
Identifiers: CVE-2026-6460 · CVE-2026-6467 · CVE-2026-14661 · CVE-2026-16237 · CVE-2026-16240 · CVE-2026-18447 · CVE-2026-116303 · CVE-2026-116304 · CVE-2026-116306 · CVE-2026-116307 · CVE-2026-116308 · CVE-2026-116309 · CVE-2026-116310 · CVE-2026-116311 · CVE-2026-116312 · CVE-2026-116313 · CVE-2026-116314 · CVE-2026-116315 · CVE-2026-116316 · CVE-2026-116317 · CVE-2026-116318 · CVE-2026-116319 · CVE-2026-116320 · CVE-2026-116321 · CVE-2026-116322 · CVE-2026-116323 · CVE-2026-116325 · CVE-2026-116326 · CVE-2026-116327 · CVE-2026-116328 · CVE-2026-116329 · CVE-2026-116330 · CVE-2026-116331 · CVE-2026-116332 · CVE-2026-116333 · CVE-2026-116335 · CVE-2026-116336 · CVE-2026-120139 · CVE-2026-120141 · CVE-2026-120142 · CVE-2026-120143 · CVE-2026-120144 · CVE-2026-120145 · CVE-2026-120146 · CVE-2026-120147 · CVE-2026-120148 · CVE-2026-120149 · CVE-2026-120150 · CVE-2026-120151 · CVE-2026-120152 · CVE-2026-120153 · CVE-2026-120154
PostgreSQL 18, PostgreSQL 17, PostgreSQL 16, PostgreSQL 15, PostgreSQL 14, PostgreSQL pg_restore client tool
On 12 November 2026 the PostgreSQL Global Development Group released updates to all supported branches, fixing 52 security vulnerabilities and more than 140 bugs. Not every fix applies to every branch, component or configuration. 14.25 is the final PostgreSQL 14 release, so 14 is now end of life. 19 RC 2 is a release candidate for testing, not the production fix.
Who is affected: Self-hosted or containerised PostgreSQL 18, 17, 16, 15 or 14 below 18.7, 17.12, 16.16, 15.20 or 14.25; any host running pg_restore from an older release; logical replication subscribers with superuser-owned subscriptions. Managed database users depend on their provider's maintenance schedule and should confirm deployment on their instance.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
Shipo 1.6 to 1.8.0: REST cookie authentication bypass allows administrator impersonation (CVE-2026-19907)
Identifiers: CVE-2026-19907
Shipo
On 14 November 2026 Wordfence disclosed CVE-2026-19907 in the Shipo WooCommerce courier plugin. In versions 1.6 through 1.8.0, the plugin's REST authentication accepts a cookie-supplied identity without a cryptographic signature. The plugin intends to apply this only to its own REST routes, but the researcher states that restriction can be bypassed, so the forged identity can be accepted on an unrelated REST endpoint. An unauthenticated attacker who knows an existing username on the site can act as that user, including an administrator, and may create accounts. The vendor fixed this in 1.8.1; the current release is 1.8.4.
Who is affected: Public WooCommerce stores with Shipo active at 1.6 through 1.8.0 and a reachable WordPress REST API. The attacker must know an existing username on the site. How easily a username can be obtained varies by site and was not verified for this briefing. Sites already on 1.8.1 or newer are not affected by this issue as described.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.