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 5 of 5
- Attention Exploitation reported
Subscribe2 stored XSS via subscriber IP value (CVE-2026-120531)
Identifiers: CVE-2026-120531
Subscribe2 – Form, Email Subscribers & Newsletters
Wordfence reports a stored cross-site scripting flaw in the Subscribe2 plugin (slug subscribe2) through version 10.47. A visitor can place script in the IP value sent by the AJAX subscription form, which is available when the popup-style signup form is enabled. The stored value is output without escaping and runs in an administrator's browser when the Subscribers list is opened. The 10.48 patched release escapes the IP and email fields on output and validates the IP. As of 9 November 2026, Wordfence also reports that its firewall has blocked attack attempts against this flaw; these are blocked attempts, not confirmed compromises.
Who is affected: Sites running Subscribe2 10.47 or earlier with the popup-style subscription form enabled, which makes the public AJAX signup flow available. Sites on the 10.48 patched release or a newer patched release carry the vendor fix.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
HestiaCP 1.10.6: security release, eight advisories now public, Ubuntu PHP source change
Identifiers: HestiaCP-1.10.6-security-release · GHSA-q3m6-6pq7-2vgr · GHSA-g8gq-6cmg-6qj8 · GHSA-whvg-4fmh-9rxg · GHSA-274c-fvrr-f3qc · GHSA-jhgf-cvhh-vr4x · GHSA-5jrh-4c42-g53q · GHSA-54r9-vp89-25w2 · GHSA-4h7f-52rq-75mj
HestiaCP and bundled File Manager
HestiaCP released 1.10.6 on 6 November 2026 as a regular, non-prerelease build with File Manager 7.16.9. The release itself carried security hardening, including a File Manager path traversal fix in 7.16.9, a root authentication check, tighter handling of POST requests in demo and read-only modes, and document root escaping. On 8 November 2026 the project separately published eight security advisories giving per-item detail on reported issues. They describe authenticated tenant-to-root command execution through proxy extensions, custom document root, FTP path changes and SSH key deletion; argument injection through tenant-controlled backup file names; cross-account file deletion during web domain restore; a read-only bypass letting a secondary administrator create a persistent API access key owned by the protected root administrator; and reflected cross-site scripting in the debug panel, which needs an authenticated victim and debug mode, off by default. None describes unauthenticated root access. The release also changes how Ubuntu PHP packages are sourced and updated.
Who is affected: Advisory metadata mostly lists versions before 1.10.5 as affected and 1.10.6 as patched, yet several narratives describe testing on 1.10.5, the custom document root advisory lists patched version 1.0.6, and the debug panel advisory lists 1.9.8 through 1.10.5 with no patched version. 1.10.6 is the security-bearing update path, not proof that every advisory is fully resolved. Each issue also has its own preconditions: the proxy extension issue needs proxy support enabled and a tenant able to edit a domain; the FTP path issue needs a web domain with an FTP account; the backup issue needs tenant-controlled mail file names and a backup run as root; the restore issue needs user-controlled paths and a restore run as root; the read-only bypass needs a secondary administrator with access to API key creation; the debug panel issue needs DEBUG_MODE set to true, which is off by default, and a logged-in victim. On Ubuntu, the release moves PHP packages to the Sury repository, migrates existing installs, and adds unattended-upgrades allowances for hosted PHP, nginx, Node, MariaDB, PostgreSQL and Apache.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
AutomatorWP privilege escalation via dynamic role data (CVE-2026-104768)
Identifiers: CVE-2026-104768
AutomatorWP – No-Code Workflow Automation, Integration & Webhooks Plugin, now with AI
Wordfence reports an unauthenticated privilege escalation flaw in the AutomatorWP plugin (slug automatorwp) through version 6.0.4. When an anonymous automation assigns a user role from dynamically supplied trigger data, such as a comment author field, an attacker can influence the role given to the created account. The 6.0.5 patched release or newer carries the fix; the current vendor release is 6.0.8.
Who is affected: Sites on AutomatorWP 6.0.4 or earlier that run an anonymous automation whose Role option is bound to attacker-influenced trigger data, such as a comment author field, and where an administrator approves the attacker's comment in the reviewed path. Both conditions must hold. The weakness sits in the role-assigning action, which did not cap the role that trigger data could set; it is not a flaw in every automatically created account, and not all automations are affected. Version 6.0.4 remains affected despite its changelog note about guarding dynamic admin creation.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
Checkout Field Editor for WooCommerce (Pro): unauthenticated attachment deletion (CVE-2026-122041)
Identifiers: CVE-2026-122041
Checkout Field Editor for WooCommerce (Pro)
Wordfence published CVE-2026-122041 on 6 November 2026 for Checkout Field Editor for WooCommerce (Pro), slug woocommerce-checkout-field-editor-pro, versions 3.8.0 and earlier, fixed in 3.8.1. This is the paid plugin, not the free woo-checkout-field-editor-pro. The vendor changelog dates 3.8.1 to 3 November 2026 and lists a fix for arbitrary attachment deletion; it also lists a separate stored cross-site scripting fix that this CVE record does not describe.
Who is affected: Sites running the Pro plugin at 3.8.0 or earlier with a configured File Upload checkout field, whose nonce is exposed in public checkout markup, and whose deletion handler lacks capability and ownership checks.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
BuddyForms plugin allows unauthenticated administrator takeover
Identifiers: CVE-2026-107622
BuddyForms
Wordfence disclosed CVE-2026-107622 on 5 November 2026 in the BuddyForms WordPress plugin, affecting versions 2.10.5 and earlier. Version 2.10.6 is patched; the vendor readme dated 19 October 2026 lists matching security fixes.
Who is affected: Only sites running BuddyForms 2.10.5 or earlier with both WordPress Anyone can register enabled and at least one public BuddyForms form attached to a page. Other WordPress sites are not affected by this issue.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
GiveWP 4.19.1 and earlier lets a settings import set Administrator as the default donor role (CVE-2026-118193)
Identifiers: CVE-2026-118193
GiveWP
In GiveWP 4.19.1 and earlier, the normal settings screen blocks Administrator as the default donor role but allows other elevated roles such as Editor. The Tools > Import JSON path bypasses that validation, so an authenticated user with the manage_give_settings capability can set Administrator as the default role for donors who register afterwards.
Who is affected: WordPress sites running GiveWP 4.19.1 or earlier. The issue requires an authenticated account that holds the manage_give_settings capability, whoever that account belongs to.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
LiteSpeed Cache can store WooCommerce cart and checkout data in public cache (CVE-2026-93389)
Identifiers: CVE-2026-93389
LiteSpeed Cache
In LiteSpeed Cache 7.9.1 and earlier, with the Cache REST option enabled as shipped by default, WooCommerce Store API cart and checkout responses can be cached publicly without varying on Cart-Token or the WooCommerce session. Later unauthenticated visitors may then receive another customer's billing, shipping and cart details, including live cart-session tokens.
Who is affected: WordPress stores running LiteSpeed Cache 7.9.1 or earlier together with WooCommerce, with the Cache REST option enabled, behind an active public LSCache layer.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
- Attention Exploitation not established
Simple CAPTCHA with Cloudflare Turnstile 1.44.3 and earlier allows stored script through a Gravity Forms shortcode (CVE-2026-93900)
Identifiers: CVE-2026-93900
Simple CAPTCHA with Cloudflare Turnstile
An authenticated user with Contributor or higher access can inject stored script through the id attribute of the [gravity-simple-turnstile] shortcode. The script runs for users who later view content containing it. This is an output-handling issue in the plugin, not a weakness in Cloudflare's Turnstile service and not a CAPTCHA bypass.
Who is affected: WordPress sites running version 1.44.3 or earlier where Contributor-level or similar accounts can submit content and the Gravity Forms integration shortcode is available. Version 1.44.4, released October 30, addresses this issue; version 1.44.5 adds separate login-form fixes that are not part of this CVE.
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.