Continue reading the full briefing.
MaxSite CMS contains a PHP object injection vulnerability that allows unauthenticated attackers to execute arbitrary code by passing attacker-controlled serialized data in the maxsite_comuser cookie directly to unserialize() without validation or class allowlisting. Attackers can craft a malicious serialized PHP object payload delivered in a single HTTP request to trigger magic methods during object graph reconstruction, enabling property-oriented…
Why it matters: CVE-2026-70554 may let attacker-controlled input cross into an interpreter or executable path, which can turn a reachable application feature into data access or code execution.
What to verify: Confirm the vulnerable route and authentication state, deploy the fixed release, review suspicious parameters and child processes, and test authorization boundaries after patching.
Operational focus: Confirm whether the vulnerable route, plugin, framework, or API behavior is enabled and public.
Open the original NIST National Vulnerability Database record
CVE-2026-70552: MaxSite CMS 109.5 and earlier contains an authentication bypass vulnerability in the…
MaxSite CMS 109.5 and earlier contains an authentication bypass vulnerability in the AJAX dispatcher that allows unauthenticated attackers to access admin-gated endpoints by supplying any X-Requested-With header and requesting a base64-encoded path resolving to any *-ajax.php file in the codebase. Attackers can exploit this dispatcher bypass to reach privileged plugin endpoints without credentials, enabling actions such as manipulating…
Why it matters: CVE-2026-70552 may sit directly on a public website, so a vulnerable core, plugin, or theme can turn a routine content system into an initial-access path.
What to verify: Record the exact WordPress core and extension versions, confirm whether the affected feature is enabled, review administrator accounts, and inspect web requests before and after the update.
Operational focus: Patch the component, test authentication and authorization boundaries, and review suspicious requests.
Open the original NIST National Vulnerability Database record
CVE-2026-7444: The Search Analytics for WP plugin for WordPress is vulnerable to Cross-Site…
The Search Analytics for WP plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.4.16. This is due to missing or incorrect nonce validation on the `process_bulk_action()` function of `MWTSA_Stats_Table`. This makes it possible for unauthenticated attackers to delete arbitrary search-term records, including all associated search-history rows, via a forged request…
Why it matters: CVE-2026-7444 may sit directly on a public website, so a vulnerable core, plugin, or theme can turn a routine content system into an initial-access path.
What to verify: Record the exact WordPress core and extension versions, confirm whether the affected feature is enabled, review administrator accounts, and inspect web requests before and after the update.
Operational focus: Use a WAF as temporary risk reduction where appropriate, but keep the permanent software fix owned.
Open the original NIST National Vulnerability Database record
CVE-2026-6627: The WPFormify – Stripe Payments with Form and Checkout plugin for WordPress…
The WPFormify – Stripe Payments with Form and Checkout plugin for WordPress is vulnerable to unauthorized modification and deletion of Stripe payment credentials in all versions up to, and including, 1.1.1. This is due to missing capability checks and nonce verification on the `wpf_stripe_callback_success()` and `wpf_stripe_disconnect()` functions, both hooked to `admin_init`. The `admin_init` hook fires on `admin-post.php` which…
Why it matters: CVE-2026-6627 may sit directly on a public website, so a vulnerable core, plugin, or theme can turn a routine content system into an initial-access path.
What to verify: Record the exact WordPress core and extension versions, confirm whether the affected feature is enabled, review administrator accounts, and inspect web requests before and after the update.
Operational focus: Confirm whether the vulnerable route, plugin, framework, or API behavior is enabled and public.
Open the original NIST National Vulnerability Database record
CVE-2026-6639: The AI Chatbot & Workflow Automation by AIWU plugin for WordPress is…
The AI Chatbot & Workflow Automation by AIWU plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.4.6. This is due to the `getCurrentTaskResults()` method in `modules/workspace/controller.php` being accessible without authentication or authorization checks. The method is not included in the workspace controller's `getNoncedMethods()` array, the base `getPermissions()` returns an empty…
Why it matters: CVE-2026-6639 may sit directly on a public website, so a vulnerable core, plugin, or theme can turn a routine content system into an initial-access path.
What to verify: Record the exact WordPress core and extension versions, confirm whether the affected feature is enabled, review administrator accounts, and inspect web requests before and after the update.
Operational focus: Patch the component, test authentication and authorization boundaries, and review suspicious requests.
Open the original NIST National Vulnerability Database record
Application response plan
Confirm that the affected route or component is actually enabled, then patch the permanent cause. Use temporary filtering only as a bridge and review requests for evidence of attempted abuse.
- Inventory WordPress core, plugins, themes, frameworks, and public API versions.
- Prioritize unauthenticated injection, authorization bypass, file access, and remote execution paths.
- Patch affected components and remove unused or abandoned extensions.
- Review web, application, authentication, and administrative change logs for abuse.
- Validate security headers, least-privilege roles, backups, and recovery after remediation.
Requests and control signals
Check route reachability, authentication state, roles, request patterns, component versions, and recovery readiness.
- Confirm whether the vulnerable route, plugin, framework, or API behavior is enabled and public.
- Patch the component, test authentication and authorization boundaries, and review suspicious requests.
- Use a WAF as temporary risk reduction where appropriate, but keep the permanent software fix owned.
Web security takeaway
Permanent web risk reduction comes from fixing the vulnerable component or authorization path, then validating the result with request evidence and recovery checks.
References used in this briefing
- CISA Known Exploited Vulnerabilities: CVE-2026-34486: Apache Tomcat Missing Encryption of Sensitive Data Vulnerability
- CISA Known Exploited Vulnerabilities: CVE-2025-68686: Fortinet FortiOS Exposure of Sensitive Information to an Unauthorized Actor Vulnerability
- NIST National Vulnerability Database: CVE-2026-5581: The Multi Uploader for Gravity Forms plugin for WordPress is vulnerable to…
- NIST National Vulnerability Database: CVE-2026-70554: MaxSite CMS contains a PHP object injection vulnerability that allows unauthenticated attackers…
- NIST National Vulnerability Database: CVE-2026-70552: MaxSite CMS 109.5 and earlier contains an authentication bypass vulnerability in the…
- NIST National Vulnerability Database: CVE-2026-7444: The Search Analytics for WP plugin for WordPress is vulnerable to Cross-Site…
- NIST National Vulnerability Database: CVE-2026-6627: The WPFormify – Stripe Payments with Form and Checkout plugin for WordPress…
- NIST National Vulnerability Database: CVE-2026-6639: The AI Chatbot & Workflow Automation by AIWU plugin for WordPress is…
Need to add context to this briefing?
Send corrections, security tips, source updates, or collaboration notes through the contact page so the editorial team can review them properly.

