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 4 of 5
- Attention Exploitation not established
Go HTTP/1 server crash from MaxBytesReader header race (CVE-2026-97054)
Identifiers: CVE-2026-97054 · GO-2026-6859
Go standard library net/http
Go 1.26.11 and 1.27.4, released 11 November 2026, fix a race in the standard net/http server. When a request body exceeds a MaxBytesReader or MaxBytesHandler limit, the server sets a Connection close header without synchronization. If the handler is reading the body while concurrently writing response headers, the program can panic and the whole process exits. Tracked as GO-2026-6859.
Who is affected: Affected: Go 1.26 before 1.26.11 and Go 1.27 before 1.27.4. The OSV range starts at version 0, so older unsupported branches are also in scope and have no current upstream fix. Only HTTP/1 serving is described, and only when a handler limits the body with MaxBytesReader or MaxBytesHandler, the body exceeds that limit, and the handler reads the body concurrently with writing response headers. The fix is in the standard library, which is compiled into each binary; a service stays affected until it is rebuilt with a patched toolchain and the new binary is deployed and restarted. Updating Go on the host alone does not patch an existing binary. A vendor-maintained toolchain that documents a backport of this fix may also count, with that vendor evidence; a version string on its own, without vendor documentation or the rebuild and redeploy evidence, does not. The eleven other fixes in the same release are build-time issues in the Go toolchain, compiler and linker, triggered by building malicious packages or build inputs. Not all require cgo: some involve directives in non-cgo Go source files or .syso object files in pure-Go packages. They affect build machines that compile untrusted code, not a running service, and are not remote code execution in a deployed binary.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
React RSC typed-array flaw enables remote code execution in Next.js 16
Identifiers: GHSA-xqc2-xf4c-x3h3 · GHSA-673q-mjm6-r5xr · CVE-2026-126187
react-server-dom-webpack, react-server-dom-turbopack, react-server-dom-parcel, Next.js
A payload framing defect in the React Server Components Flight transport (react-server-dom-webpack, -turbopack, -parcel) can, in extremely rare responses containing multiple typed arrays and an attacker-controlled value, lead to unauthenticated server code execution. Next.js 16.0.0 to 16.4.0 is affected when App Router, Cache Components, and a use cache function returning multiple typed arrays are combined. Client-only React without server or RSC support is out of scope. The React advisory now carries CVE-2026-126187.
Who is affected: Affected react-server-dom packages: 19.0.0 to 19.0.8, 19.1.0 to 19.1.9, 19.2.0 to 19.2.8, and 19.3.0; fixed in 19.0.9, 19.1.10, 19.2.9, and 19.3.1. Next.js 16.0.0 to 16.4.0 is fixed in 16.4.1. Next.js 15.x is not listed as affected by this advisory; the official post recommends 15.5.28, which carries the upstream transport fix plus a separate image fix. The React advisory GHSA-xqc2-xf4c-x3h3 now carries CVE-2026-126187 and was confirmed in GitHub's global advisory database at review; what npm audit actually reports was not tested, so a clean audit is not clearance. The Next.js advisory GHSA-673q-mjm6-r5xr still has no CVE.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
ARForms 7.2.4 and earlier (CVE-2026-111190): unauthenticated arbitrary file upload through a public File field
Identifiers: CVE-2026-111190
ARForms
ARForms versions up to 7.2.4 let an unauthenticated visitor submit a published public form containing a File field with a crafted filename or header that bypasses the upload checks, placing an executable PHP file in a public directory. Wordfence tracks this as CVE-2026-111190. Remote code execution is possible, subject to the server's execution configuration. ARForms Lite is a separate product and is not covered by this range.
Who is affected: Sites running the ARForms plugin at 7.2.4 or earlier with at least one published, publicly accessible form that includes a File field.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
Everest Forms 3.6.3 and earlier (CVE-2026-115483): unauthenticated local file read by email through signature-keyed attachments
Identifiers: CVE-2026-115483
Everest Forms
Wordfence reports that Everest Forms through 3.6.3, when the Pro add-on is active and Attach Files is enabled on an email notification, can attach an arbitrary local file to a notification whose recipient the submitter controls, when any field's meta key contains the text signature_. The public CNA record for CVE-2026-115483 corroborates this description. Files such as wp-config.php could be mailed to an attacker-supplied address. No standalone code execution is claimed, and Wordfence lists no known patch.
Who is affected: Sites running Everest Forms 3.6.3 or earlier with the Pro add-on, an email notification using Attach Files, any field whose meta key contains signature_ (a plain text field labelled Signature is the reporter's example; a genuine signature-type field is not required), and a notification recipient routed from submitter input. If any precondition is absent, the described path does not apply.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
Ninja Forms File Uploads 3.3.36 and earlier (CVE-2026-126537): unauthenticated file deletion via the background upload path
Identifiers: CVE-2026-126537
Ninja Forms - File Uploads
The paid File Uploads add-on for Ninja Forms, through version 3.3.36, lets an unauthenticated public submission pass an untrusted local file path into its background upload handling. Wordfence reports arbitrary file deletion and potential file read through configured S3, Dropbox or Google Drive storage, tracked as CVE-2026-126537. Ninja Forms core is not the affected product.
Who is affected: Sites running the File Uploads add-on at 3.3.36 or earlier with a publicly submittable form that uses the background upload path. The role of any configured external storage needs per-site assessment.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation reported
Xen Orchestra: actively exploited authentication bypass via empty-object token lookup on the REST interface
Identifiers: VSA-2026-062
Xen Orchestra / Xen Orchestra Appliance
Vates advisory VSA-2026-062, published and updated 10 November 2026 and rated critical, describes an authentication bypass in the Xen Orchestra REST interface. A malformed empty-object lookup is not filtered, so it returns the first token in the store; if that token is unexpired, the request is accepted and the unauthenticated requester acts as that token's user. Vates states the flaw is being actively exploited. The reviewed vendor advisory does not name a CVE as of this check. Xen Orchestra before 6.9.2 (stable) and 6.10.1 (latest) is affected, including the Xen Orchestra Appliance. Fixed releases are 6.9.2 stable and 6.10.1 latest, with xo-server 5.211.2 stable and 5.213.1 latest. Source installs should move to the current patched master per vendor guidance; the fix is tracked in pull request 10748.
Who is affected: Xen Orchestra or XOA instances running an affected, unpatched build (before 6.9.2 stable or 6.10.1 latest, or a source build predating the fix), whose REST interface an attacker can reach, and where the first token returned by the unfiltered lookup is unexpired. Patched builds are not affected. Internet-exposed instances carry the highest risk; VPN-only reachability is not automatically safe.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
Everest Forms: unauthenticated deletion of files inside uploads under specific add-on settings (CVE-2026-120513)
Identifiers: CVE-2026-120513
Everest Forms
Wordfence published a notice on 9 November 2026 for the Everest Forms plugin (slug everest-forms) covering all versions up to and including 3.6.2, with a fix in 3.6.3. The vendor changelog for 3.6.3, dated 15 October 2026, records improved security of file deletion when processing uploaded submissions. The current stable release is 3.6.4, dated 5 November 2026. The weakness is insufficient path validation in the routine that removes a CSV file after an email is sent, which can allow a visitor without an account to delete files inside the wp-content/uploads directory.
Who is affected: Only sites running Everest Forms 3.6.2 or earlier where the Save and Continue add-on is active (the EVF_SAVE_AND_CONTINUE_VERSION constant is defined) and the target form has the Disable storing entry information setting enabled. Sites that do not meet both conditions are not affected as described.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation reported
GPUStack: loopback trust allows unauthenticated administrator access, now listed as known exploited (CVE-2026-102895, GHSA-gj9m-f8ph-pmhr)
Identifiers: CVE-2026-102895 · GHSA-gj9m-f8ph-pmhr
GPUStack / gpustack
The GPUStack project published its advisory on 31 July 2026 and updated it on 29 September 2026. On 9 November 2026 CISA added the issue to its Known Exploited Vulnerabilities catalog; this is a new listing, not a new vulnerability. Affected is GPUStack (the gpustack package) before 2.2.0, regardless of how it was installed; pip is the ecosystem named in the advisory, but container deployments running the same vulnerable gpustack code can be affected too. The verified vendor fix is 2.2.0. With the default setting force_auth_localhost set to false, requests that appear to come from the local machine are automatically trusted as an administrator. A reverse proxy running on the same host can make external traffic appear local without any forged header, and a client-controlled X-GPUStack-Real-IP header can also influence the recorded source address.
Who is affected: Small and medium businesses running GPUStack as part of AI infrastructure behind a website or application, not websites in general. Most exposed are deployments before 2.2.0 with the default localhost trust and a same-host reverse proxy or any reachability from untrusted networks.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
Ultra Addons for Contact Form 7: unauthenticated file read through PDF generation when a PDF template is enabled (CVE-2026-100386)
Identifiers: CVE-2026-100386
Ultra Addons for Contact Form 7
Wordfence published a notice on 9 November 2026 for Ultra Addons for Contact Form 7 (repository name UltimateAddons, slug ultimate-addons-for-contact-form-7), affecting versions up to and including 3.5.54 and fixed in 3.5.55. This is a different issue from the earlier CVE-2026-102435 object injection and deletion problem already covered. The weakness is directory traversal in the mail components routine when mPDF processes SVG content during HTML rendering, allowing a visitor without an account to read arbitrary files on the server. The vendor changelog for 3.5.55, dated 11 October 2026, states that issues reported by Wordfence were resolved; 3.5.57, dated 1 November 2026, adds PDF filename sanitization and more secure mPDF handling and is the current stable release.
Who is affected: Only sites running 3.5.54 or earlier with the PDF Generator add-on active and an administrator-configured PDF body template enabled for the targeted contact form. Not every Contact Form 7 installation is affected; sites without this plugin or without an enabled PDF template are out of scope as described.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Withdrawn
OpenSSH password bypass on Alpine musl systems without PAM
Identifiers: OpenSSH-musl-password-bypass-2026-11-05 · CVE-2026-123158
OpenSSH on Alpine Linux / musl
Reason for withdrawal: This guidance has been withdrawn while it is rechecked and must not be relied on. See the dated history for this entry and the original advisory.
- Last substantive change
- Last verified
- Attention Exploitation not established
BackUpWordPress: logged-in users can delete backup protection files, fixed in 3.15
Identifiers: CVE-2026-104307
BackUpWordPress
BackUpWordPress, plugin slug backupwordpress, lacks a capability and nonce check on the AJAX action used to dismiss error notices in versions before 3.15, tracked as CVE-2026-104307. Any authenticated user, including the Subscriber role, can trigger it to delete files in the backup directory: the .htaccess file that protects backups from direct download, and working files such as database dumps still in progress. WPScan published the issue on 6 November 2026, the CVE record followed on 8 November, and the vendor changelog for 3.15 is dated 4 November 2026.
Who is affected: Sites running BackUpWordPress below 3.15 with any authenticated account, including the Subscriber role; a single-user site is affected if that one account is compromised. Multiple accounts or open registration, such as customers and commenters, increase the risk but are not required. Sites on 3.15 or newer have the fix, but updating does not by itself establish that missing files are restored or that older backup copies are protected; verify the download rules and backup integrity separately.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
Productive Commerce Wishlist plugin: unauthenticated SQL injection fixed in 1.1.54
Identifiers: CVE-2026-109925
Productive Commerce Wishlist Compare MiniCart
The Productive Commerce Wishlist Compare MiniCart plugin for WooCommerce, plugin slug productive-commerce, has an SQL injection flaw tracked as CVE-2026-109925. WPScan published it on 6 November 2026 and updated the entry on 7 November; the CVE record followed on 8 November. The vendor changelog for 1.1.54, dated 4 November 2026, says it fixed an SQL vulnerability when deleting wishlisted or comparison products. The affected code sits in wishlist and compare handlers that work without a login. Versions before 1.1.54 are affected and 1.1.54 fixes the issue.
Who is affected: Any WooCommerce site with this plugin active at a version below 1.1.54. Sites without the plugin, or already on 1.1.54 or a newer patched release, are not affected by this issue.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.