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 2 of 5
- Attention Exploitation not established
Next.js 16.4.5 and 15.5.29 close five moderate advisories covering cookies, images, response handling and cache privacy
Identifiers: CVE-2026-119346 · GHSA-f3mh-rxg3-f5g2 · CVE-2026-119347 · GHSA-7qx7-33qx-rqx2 · CVE-2026-119348 · GHSA-pc58-hwjq-p385 · CVE-2026-119349 · GHSA-rhh4-g77r-r9qj · CVE-2026-119350 · GHSA-vvgp-ww4w-46vf
Next.js Edge runtime cookie handling (CVE-2026-119346), Next.js Self-hosted image optimization (CVE-2026-119347), Next.js Self-hosted upstream response forwarding (CVE-2026-119348), Next.js App Router cache keys with binary arguments (CVE-2026-119349), Next.js Cache Components shared fallback (CVE-2026-119350)
On 19 November 2026 Vercel published five security advisories for Next.js, each rated moderate by the vendor, with fixes in 16.4.5 and backports in 15.5.29 where a 15.x line is affected. This is a separate November 19 event and is independent of the earlier React Server Components issues. The advisories group into four areas: Edge runtime cookie handling, the self-hosted image optimizer, unchanged upstream responses behind an HTTP/1.1 reverse proxy, and cache privacy in the App Router. Several paths touch confidentiality, which is why a single conditional update deserves attention even at a moderate rating. Information checked on 20 November 2026.
Who is affected: Fixed versions are 16.4.5 for all five advisories and 15.5.29 for the three that reach the 15.x line (CVE-2026-119346, CVE-2026-119347 and CVE-2026-119348). The two cache advisories, CVE-2026-119349 and CVE-2026-119350, apply only to 16.x, and CVE-2026-119350 only from 16.4.0. Three of the five conditions expressly concern self-hosted deployments: the image optimizer under CVE-2026-119347, the reverse proxy path under CVE-2026-119348, and next start with Cache Components under CVE-2026-119350. The other two depend on feature use rather than hosting model: CVE-2026-119346 applies where an Edge runtime route sets cookies through NextResponse, and CVE-2026-119349 where App Router functions use the use cache directive with binary arguments. Managed and self-hosted deployments should be checked separately against the vendor conditions; this briefing does not claim that any managed platform is or is not affected beyond those conditions. Exposure is determined by the version actually running in each build and whether the relevant feature path is in use. The resolved version in the lockfile is one check, not the deciding fact.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
HestiaCP 1.10.8: local 2FA QR generation and three maintainer advisories on backup access, impersonation redirect and reset logging
Identifiers: HestiaCP-1.10.8-security-release · GHSA-784f-pcj8-rqxp · GHSA-76m3-mq7g-jc97 · GHSA-4qc9-p3qr-434q
HestiaCP panel (external QR generation), HestiaCP backup downloads, HestiaCP admin redirect, HestiaCP reset logging
HestiaCP published release 1.10.8 on 18 November 2026. Its Security section lists three changes: 2FA QR codes are now generated locally with bacon/bacon-qr-code 3.1.1 instead of through an external QR service, and the panel refuses to save a broken 2FA secret (#5869); the post-login redirect now stays within the panel (#5990); and users can only download their own backup archives, not other files that merely start with their username (#5990). The release also bundles Nginx 1.30.7 and SnappyMail 3.1.3, adds a Hestia-specific Dovecot Fail2Ban filter with maxretry 10, and makes the password and 2FA reset pages opened from an email link always carry a CSRF token. On 19 November 2026 the maintainers published three advisories that link to these changes: GHSA-784f-pcj8-rqxp on cross-account backup access, GHSA-76m3-mq7g-jc97 on an open redirect during legitimate admin impersonation, and GHSA-4qc9-p3qr-434q on failed reset logging and rate limiting. A later 1.10.9 release carries a security-bearing PHP runtime update that is tracked as a separate PHP incident. Checked as of 20 November 2026.
Who is affected: GHSA-784f-pcj8-rqxp lists affected <1.10.7 and fixed 1.10.8; the notice does not settle how 1.10.7 behaves for this bug. GHSA-76m3-mq7g-jc97 lists affected 1.10.7 and fixed 1.10.8. GHSA-4qc9-p3qr-434q lists affected 1.10.7 and fixed 1.10.8, but its description reports a reproduction on 1.10.5, so the published range and the reproduction differ and the exact earlier range is uncertain. The 2FA QR change carries no completed affected range and no advisory. Relevance also depends on workflow: the 2FA item matters where accounts enrolled 2FA through the panel QR code, the redirect item concerns administrators who access the panel as a user, the backup item concerns panel users who download backups on hosts with legacy overlapping usernames, and the reset item concerns the password and 2FA reset pages. 1.10.8 is the containing fix; use a supported vendor update that includes it. A new panel version number does not by itself show that bundled or separate runtimes were patched, and no other package fix should be inferred from the 1.10.9 release title.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
WordPress 7.1.5 security release: 20 listed security and hardening items, Template Part escalation now confirmed by a vendor advisory
Identifiers: WordPress-7.1.5-security-release · GHSA-pmp8-6cv8-q323
WordPress core (November 18 release set), WordPress Template Part block
On 18 November 2026 the WordPress project released 7.1.5 as a security release. The release post and HelpHub list 20 security and hardening items. That is 20 entries on one list, not 20 separate CVEs. The items include a template-related privilege escalation, two SQL injection fixes, a multisite privilege escalation, several cross-site scripting and data disclosure fixes, and denial-of-service fixes. The earlier version of this briefing already confirmed the 7.1.5 release. Since then the Template Part escalation has received a published vendor advisory, GHSA-pmp8-6cv8-q323, which corroborates the release notes. The advisory lists WordPress 7.1.0 through 7.1.4 as affected and 7.1.5 as fixed, and states that the fix for this particular issue was backported to older branches back to 5.9, for example 7.0.9, 6.9.12 and 5.9.21. The general release archive now confirms 18 November security builds for older branches, including 4.7.40, which the earlier briefing had not yet confirmed. Do not read the archive as meaning every fix reached every older branch, or that the Template Part issue exists on 4.7. WordPress asks site owners to update immediately.
Who is affected: Applies to any self-hosted or managed WordPress site running 7.1.0 through 7.1.4. Sites on older branches are also in scope. The Template Part fix was backported down to 5.9, and the archive lists 18 November security builds for other older lines such as 4.7.40. Those older builds are courtesy releases and do not establish ongoing support for those branches. Managed hosts and sites with automatic core updates may already be on 7.1.5. Confirm rather than assume. The release candidate line is not a production recommendation. In production, prefer the stable 7.1.5 build and check the current official guidance on supported updates and branches.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation reported
Optimizely Web Experimentation: malicious code injected into customer Project JavaScript through a signup-flow flaw
Identifiers: Optimizely-Web-Experimentation-November-2026-incident
Optimizely Web Experimentation
On 16 November 2026, attacker-written code appeared in the Project JavaScript of some Optimizely Web Experimentation customer projects. Each affected snippet still loaded from Optimizely's CDN or a customer's own self-hosted path, so the code reached visitors through the snippet itself. Optimizely's status page update of 18 November 2026, 14:49 UTC, says an unauthorized third party exploited a flaw in the Web Experimentation account signup flow, used it to impersonate users on targeted customer accounts, and inserted malicious JavaScript into those customers' projects. Optimizely says it detected the activity on the day it began, blocked delivery of the malicious code, closed the vulnerability within three hours of detection, and removed the injected code from all affected projects. It states this was not a credentials breach, that the incident was limited to Web Experimentation, that fewer than 5% of its customers were impacted, and that it has contacted every Web Experimentation customer directly to confirm whether they were affected and to provide additional guidance. As of 19 November the incident is still listed as monitoring, not resolved.
Who is affected: Optimizely says it has contacted every Web Experimentation customer directly with their status and guidance, and that customers who do not use Web Experimentation need do nothing. If your site loads a Web Experimentation snippet, from cdn.optimizely.com or a self-hosted copy, make sure that message reached whoever owns your Optimizely account, and confirm the result yourself rather than relying on the vendor statement alone. If Optimizely confirms your project was modified, or you find modified code in it, your visitors were exposed during the interval that modified snippet was served, and the exposure steps below apply. Fewer than 5% of customers were affected according to Optimizely, so check your own project rather than assuming either way.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
nginx 1.31.9 and 1.30.7 fix five memory corruption flaws in HTTP/2, HTTP/3, resolver and mail proxy paths
Identifiers: CVE-2026-123007 · CVE-2026-123633 · CVE-2026-123634 · CVE-2026-121810 · CVE-2026-113425
NGINX Open Source (CVE-2026-123007), NGINX Open Source (CVE-2026-123633), NGINX Open Source (CVE-2026-123634), NGINX Open Source (CVE-2026-121810), NGINX Open Source (CVE-2026-113425)
On 18 November 2026 the nginx project released 1.31.9 and stable 1.30.7, fixing five separate memory corruption issues (CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810, CVE-2026-113425). Researchers call the set nginx2root; that is a research label, not a finding that the flaws grant root. Each issue needs its own feature path to be enabled and reachable.
Who is affected: Official nginx index ranges: CVE-2026-123007 1.9.5–1.31.8; CVE-2026-123633 1.19.7–1.31.8; CVE-2026-123634 0.6.18–1.31.8; CVE-2026-121810 1.25.0–1.31.8; CVE-2026-113425 0.5.33–1.31.8. Fixed in 1.31.9 or stable 1.30.7. Distribution and vendor builds may backport fixes under older version numbers, so a version banner alone is not proof. NGINX Plus is packaged separately and is not covered here.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
WP Duplicate migration plugin: unauthenticated file read and subscriber-to-administrator sync hijack, no known patch
Identifiers: CVE-2026-14491 · CVE-2026-85776
WP Duplicate – WordPress Migration Plugin
Wordfence published two records on 18 November 2026 for WP Duplicate – WordPress Migration Plugin up to 1.1.11. CVE-2026-14491 lets an unauthenticated attacker read arbitrary server files via the file_name parameter, because a loose comparison on the stored secret can be bypassed without knowing it. CVE-2026-85776 is missing authorization on several AJAX actions, letting a Subscriber-level user rewrite the plugin's prod_site_url setting to an attacker-controlled host and enumerate server directories. Code execution happens only if an administrator later triggers a sync: the site then fetches an unsigned attacker-supplied ZIP and extracts it through a bridge under the web root that works independently of WordPress.
Who is affected: WordPress sites with WP Duplicate (plugin slug local-sync) 1.1.11 or earlier installed, whether or not migration is in active use. No fixed version is known; the vendor readme and the CNA record both returned 404 when checked on 19 November 2026.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
WP STAGING and WP STAGING Pro: subscriber-planted serialized object can run code when an administrator later restores or resets
Identifiers: CVE-2026-109555
WP STAGING Free, WP STAGING Pro
Wordfence published on 18 November 2026 a PHP object injection in WP STAGING Free up to 4.17.0 and WP STAGING Pro up to 6.17.0 (CVE-2026-109555). The database importer treats text beginning with {WPSTG_BINARY} as trusted internal binary data and decodes its hexadecimal suffix into serialized bytes. A Subscriber-level user can store such text in their own profile. If an administrator later performs an ordinary database-including restore or staging reset that contains that value, and the restored profile metadata is loaded, either during the restore or in a later request, a built-in gadget chain can execute arbitrary code.
Who is affected: WordPress sites running WP STAGING Free 4.17.0 or earlier, or Pro 6.17.0 or earlier, that have untrusted low-privilege accounts and use database restore or staging reset. This is a different plugin and CVE from the recently covered UpdraftPlus issue, and it is not a WordPress core fix.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
Java4Shell (CVE-2026-114938): out-of-bounds write in the OpenJDK Base64 decoder intrinsic
Identifiers: CVE-2026-114938
Oracle Java SE 17, Oracle Java SE 21, Oracle Java SE 25, Oracle Java SE 27, Oracle Java SE 8-perf, Oracle GraalVM
Oracle's 17 November 2026 update fixes CVE-2026-114938, a Compiler component flaw that Datadog Security Labs calls Java4Shell. The optimized Base64 decoder can write out of bounds when a vulnerable runtime decodes attacker-controlled data on an x86-64 CPU that takes the AVX-512 VBMI path. Oracle Java SE 17, 21, 25 and 27 have fixed releases. Oracle Java SE 8u511b33-perf and Oracle GraalVM are listed as affected without an independently verified CVE-specific fixed build.
Who is affected: Oracle's CNA entry lists exact affected builds: Java SE 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3; GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3; GraalVM Enterprise Edition 21.3.20.0.3. Datadog describes a wider range of OpenJDK builds, for example Java 17 from 17.0.6 until releases before 17.0.21.1, so the two sources differ in both format and scope. Exploitation also requires an x86-64 CPU with AVX-512 VBMI and a code path where attacker-controlled Base64 reaches the affected decoder; native ARM64 JVMs do not execute this path according to Datadog. Ordinary Java 8 and Java 11 builds are not listed for this CVE, but the 8-perf listing means Java 8 is not a blanket all-clear, and other fixes in the November update are separate.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
Magic Login Mail or QR Code 2.07 and earlier: Host header can shape the emailed login link (CVE-2026-126721)
Identifiers: CVE-2026-126721
Magic Login Mail or QR Code
Wordfence Intelligence reports that the plugin builds its magic-login link from the raw Host header when the current page has no permalink. An attacker-controlled hostname can then appear in the link emailed to an administrator. Version 2.08, dated 12 November 2026 in the vendor changelog, fixes link generation.
Who is affected: All of these must be true at once: the magic_login shortcode renders on a path with no permalink, such as a 404 page or a block theme header part; the web server forwards non-canonical Host headers; the attacker knows the administrator's email address; and the administrator clicks the tampered link. A fully automatic takeover without administrator interaction is not established by the source.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
rus to lat advanced 1.1 and earlier: unauthenticated SQL injection, no known patched version (CVE-2026-115815)
Identifiers: CVE-2026-115815
rus to lat advanced
Wordfence Intelligence reports a blind SQL injection through the name parameter in rus to lat advanced, all versions up to and including 1.1. The notice lists no patched version, and the plugin readme changelog has no entry beyond 1.1. Until a fixed version appears, mitigation falls to the site owner.
Who is affected: Any site where the plugin is installed and active. The affected handler is reachable without an account. Sites that use it to transliterate Cyrillic titles into Latin slugs are the typical case.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
UpdraftPlus restore path: subscriber profile text can alter a later database restore (CVE-2026-108761)
Identifiers: CVE-2026-108761
UpdraftPlus
Wordfence published CVE-2026-108761 on 18 November 2026 for the UpdraftPlus backup plugin. A logged-in user with only a subscriber role can place crafted text in their profile description. That text is captured in a database backup and, when an administrator later restores the backup on a vulnerable version, is processed as SQL. The vendor released Free 1.26.16 and Premium 2.26.16 on 16 November 2026.
Who is affected: UpdraftPlus Free up to and including 1.26.15, and Premium 2.0.0 through 2.26.15. Most relevant for sites that allow public registration or hold many low-privilege accounts and that rely on UpdraftPlus database restores.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
Git: cloning a malicious repository can run attacker code, including non-recursive clones
Identifiers: CVE-2026-111760 · GHSA-vp2w-7xxj-jvxr
Git
CVE-2026-111760 (GHSA-vp2w-7xxj-jvxr) is an integer truncation bug in Git's index handling. An attacker-controlled server can supply trees whose combined path lengths overflow the cache-entry name-length field, letting checkout overwrite .git despite path validation and redirect Git to attacker-controlled configuration or hooks. The Git project advisory, updated 17 November 2026 20:45 UTC, now states exploitation is not limited to recursive clones. In a recursive clone, code can run during the clone itself. In a non-recursive clone, the top-level .git directory can be replaced by a gitfile pointing to attacker-supplied metadata; the clone can then fail and suggest running git status, and following that suggestion can execute attacker code through core.fsmonitor. The advisory now lists concrete affected and patched ranges, replacing the placeholder metadata noted in our 11 November briefing.
Who is affected: Affected per the project advisory: Git 2.50.1 and earlier, 2.51.0 to 2.51.2, 2.52.0, 2.53.0, 2.54.0, 2.55.0 and 2.56.0. Fixed in 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1 and 2.56.1, or a distributor security backport. GitHub's server-side fixes do not patch local Git, bundled clients or CI images. At the time of this review, Ubuntu's tracker shows 'Needs evaluation' for every listed release, including Noble and Jammy; this means a fixed Ubuntu package revision has not yet been verified in this review, not that one will not be issued. Once Canonical publishes a security notice, that notice takes precedence over any raw upstream version comparison. GitHub Enterprise Server administrators should use 3.19.16, 3.20.12, 3.21.10 or 3.22.5, whose bundled Git version numbers differ from the upstream releases above.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.