---METADATA---
VENDOR: WordPress
PRODUCT: MailChimp Subscribe Form, Optin Builder, PopUp Builder, Form Builder
AFFECTED_VERSIONS: 0 through 4.3.3
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
The MailChimp Subscribe Form, Optin Builder, PopUp Builder, Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Form Field Values.

Executive Summary:
An unauthenticated Stored Cross-Site Scripting vulnerability in the MailChimp Subscribe Form plugin allows attackers to inject malicious scripts into form fields, potentially compromising user sessions.

Vulnerability Details

CVE-ID: CVE-2026-15052

Affected Software: WordPress MailChimp Subscribe Form, Optin Builder, PopUp Builder, Form Builder

Affected Versions: 0 through 4.3.3

Vulnerability: This is a Stored Cross-Site Scripting (XSS) vulnerability caused by improper neutralization of user-supplied input within form field values. The vulnerability is exploitable by unauthenticated remote attackers.

Business Impact

The vulnerability allows for the execution of arbitrary JavaScript in the browser of a victim, such as a WordPress administrator. Successful exploitation could lead to session hijacking, unauthorized administrative actions, or the redirection of users to malicious sites, severely impacting the integrity and security of the WordPress instance. The CVSS score of 7.2 reflects the high risk associated with this unauthenticated remote access vector.

Remediation Plan

Immediate Action: Update the MailChimp Subscribe Form, Optin Builder, PopUp Builder, Form Builder plugin to version 4.3.4 or later.

Proactive Monitoring: Monitor WordPress administrative access logs for suspicious activity or unauthorized script execution patterns originating from form submissions.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to block common XSS payloads and malicious script injections in POST requests.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of August 2, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. Stored XSS flaws are inherently dangerous as they can trigger execution automatically when an administrator views the compromised data.

Analyst Recommendation

Given the ease of exploitation and the potential for full administrative account takeover, organizations using this plugin must prioritize the update to version 4.3.4 immediately. Failure to patch leaves the platform exposed to potential cross-site scripting attacks that can compromise sensitive user data and site configuration.

---METADATA---
VENDOR: WordPress
PRODUCT: Geeky Bot
AFFECTED_VERSIONS: 0 up to (excluding) 1.2.8
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
The Geeky Bot WordPress plugin is susceptible to an information exposure vulnerability allowing unauthenticated remote attackers to access sensitive data.

Executive Summary:
An information exposure vulnerability in the Geeky Bot WordPress plugin allows unauthenticated attackers to access sensitive information, posing a high risk to data confidentiality.

Vulnerability Details

CVE-ID: CVE-2026-15048

Affected Software: WordPress Geeky Bot

Affected Versions: 0 up to (excluding) 1.2.8

Vulnerability: This is an information exposure vulnerability (CWE-200) affecting the Geeky Bot plugin. It allows unauthenticated attackers to retrieve sensitive information from the application due to improper access controls.

Business Impact

With a CVSS score of 7.5, this vulnerability represents a significant threat to data privacy. Unauthorized access to information handled by the plugin could lead to the compromise of proprietary data, customer information, or system configuration details.

Remediation Plan

Immediate Action: Update the Geeky Bot plugin to version 1.2.8 or later immediately.

Proactive Monitoring: Monitor site traffic for anomalous GET requests that attempt to access sensitive plugin-related files or data paths.

Compensating Controls: Use a Web Application Firewall to filter out suspicious requests that attempt to enumerate or access internal plugin resources.

Exploitation Status

Public Exploit Available: No (exploit_available: false)

Analyst Notes: As of August 1, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The vulnerability is highly automatable, increasing the likelihood of opportunistic scanning by malicious actors.

Analyst Recommendation

The high severity of this vulnerability necessitates immediate patching. Security teams should verify the current version of the Geeky Bot plugin across all WordPress instances and apply the necessary updates to prevent potential data leakage.

---METADATA---
VENDOR: HMBRAND
PRODUCT: DBI::SQL::Nano
AFFECTED_VERSIONS: 1.42 up to (excluding) 1.651
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
DBI::SQL::Nano for Perl incorrectly evaluates SQL WHERE predicates, leading to inverted comparisons for <= and >= operators.

Executive Summary:
A logic error in the DBI::SQL::Nano engine causes incorrect evaluation of SQL comparison operators, potentially leading to unauthorized data access or policy bypass.

Vulnerability Details

CVE-ID: CVE-2026-15043

Affected Software: HMBRAND DBI::SQL::Nano

Affected Versions: 1.42 up to 1.651

Vulnerability: This vulnerability involves the use of incorrect operators (CWE-480) within the is_matched method of the SQL engine. The <= and >= operators are improperly mapped to Perl comparison logic, causing queries to return incorrect data sets when filtering file-backed tables.

Business Impact

The business impact is significant when the software is used to enforce security policies or authorization logic via database queries. With a CVSS score of 9.8, the silent failure of these comparisons could result in unauthorized data exposure or the failure of critical integrity checks, potentially violating compliance requirements.

Remediation Plan

Immediate Action: Upgrade the DBI module to version 1.651 or later to resolve the operator inversion logic.

Proactive Monitoring: Review application-level logs and database query results for unexpected filtering behavior or records that should have been excluded by security predicates.

Compensating Controls: Audit any application code that relies on DBI::SQL::Nano for authorization or sensitive data filtering to ensure that logic remains sound until patching is completed.

Exploitation Status

Public Exploit Available: No (exploit_available: false)

Analyst Notes: As of July 14, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The risk is primarily driven by the potential for logic errors in security-sensitive applications.

Analyst Recommendation

While this is a logic-based flaw rather than a traditional injection, the impact on data integrity is severe. Organizations relying on file-backed DBI drivers should verify their version and apply the update as soon as possible.

---METADATA---
VENDOR: Unknown
PRODUCT: giftware
AFFECTED_VERSIONS: 0 up to 4.2.10
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
The giftware WordPress plugin contains an unrestricted file upload vulnerability, allowing unauthenticated users to upload malicious files and execute arbitrary code.

Executive Summary:
An unauthenticated remote code execution vulnerability in the giftware WordPress plugin allows attackers to upload and execute arbitrary files on the server.

Vulnerability Details

CVE-ID: CVE-2026-15039

Affected Software: giftware (WordPress plugin)

Affected Versions: 0 up to (excluding) 4.2.10

Vulnerability: The plugin fails to perform adequate file type validation on one of its upload paths. This allows unauthenticated users to upload arbitrary files, including malicious PHP scripts, resulting in remote code execution on the hosting server.

Business Impact

The CVSS score of 9.8 reflects the ease of exploitation and the high impact on confidentiality, integrity, and availability. Successful exploitation grants an attacker full control over the web application, facilitating data exfiltration, malware distribution, or complete server takeover.

Remediation Plan

Immediate Action: Update the giftware plugin to version 4.2.10 or later immediately.

Proactive Monitoring: Audit the server for any uploaded files in the plugin's upload directories and check for signs of unauthorized access or backdoors.

Compensating Controls: Use a WAF to block unauthorized file uploads and restrict access to the affected directory by disabling direct script execution via server configuration files (such as .htaccess).

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of August 12, 2026, there is no confirmed active exploitation in the wild: however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. Unrestricted file upload flaws are trivial to exploit once identified and are frequently targeted by automated scanners.

Analyst Recommendation

Due to the critical nature of this vulnerability, immediate remediation is required. If an update cannot be applied immediately, the plugin should be deactivated and removed from the environment to eliminate the attack vector until a patch is deployed.

---METADATA---
VENDOR: InfiniteWP
PRODUCT: InfiniteWP Client
AFFECTED_VERSIONS: before 1.13.6
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
The InfiniteWP Client WordPress plugin fails to verify request authenticity, allowing unauthenticated attackers to hijack administrator sessions and achieve remote code execution.

Executive Summary:
A critical vulnerability in the InfiniteWP Client plugin allows unauthenticated attackers to hijack administrative sessions and gain full control over affected WordPress Multisite networks.

Vulnerability Details

CVE-ID: CVE-2026-15038

Affected Software: InfiniteWP InfiniteWP Client

Affected Versions: before 1.13.6

Vulnerability: This is an improper authentication vulnerability occurring within the remote-management endpoint of the plugin. Unauthenticated remote attackers can bind their own keys to the site, bypassing security controls to hijack administrator sessions.

Business Impact

The CVSS score of 9.8 reflects the extreme severity of this flaw, which grants attackers total control over the affected environment. Successful exploitation leads to a complete site takeover, unauthorized access to sensitive data, and the execution of arbitrary code, which could result in severe reputational damage and long-term security compromise.

Remediation Plan

Immediate Action: Update the InfiniteWP Client plugin to version 1.13.6 or later immediately.

Proactive Monitoring: Monitor server access logs for unusual requests directed at the remote-management endpoint, particularly those originating from unknown or unauthorized IP addresses.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to block suspicious traffic patterns targeting WordPress management endpoints until the update can be applied.

Exploitation Status

Public Exploit Available: Yes, a public proof-of-concept repository is available on GitHub.

Analyst Notes: As of Aug 9, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The flaw is highly accessible, requiring no authentication to trigger.

Analyst Recommendation

Given the ease of exploitation and the potential for full system compromise, this vulnerability poses an immediate threat to any organization utilizing the InfiniteWP Client. Administrators must prioritize patching to version 1.13.6 across all affected WordPress Multisite instances to mitigate the risk of unauthorized access and remote code execution.

---METADATA---
VENDOR: WordPress
PRODUCT: MDJM Event Management
AFFECTED_VERSIONS: 0 through 1.7.8.4
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
The MDJM Event Management plugin for WordPress suffers from an improper privilege management vulnerability, allowing authenticated users to escalate their privileges.

Executive Summary:
A critical privilege escalation vulnerability in the MDJM Event Management plugin for WordPress, rated as High severity, allows authenticated users to gain unauthorized administrative access.

Vulnerability Details

CVE-ID: CVE-2026-15017

Affected Software: WordPress MDJM Event Management

Affected Versions: 0 through 1.7.8.4

Vulnerability: This vulnerability is classified as CWE-269 (Improper Privilege Management). It allows an attacker who already possesses low-level authenticated access to the system to escalate their permissions, potentially gaining full control over the plugin functions.

Business Impact

With a CVSS score of 8.8, this vulnerability poses a severe risk to business operations. Unauthorized privilege escalation can lead to total system compromise, including the exfiltration of sensitive event data, unauthorized financial transactions, or complete site takeover.

Remediation Plan

Immediate Action: Update the MDJM Event Management plugin to version 1.7.8.5 or later immediately.

Proactive Monitoring: Monitor site traffic and database logs for suspicious queries originating from low-privileged accounts that attempt to access restricted administrative functions.

Compensating Controls: Implement a Web Application Firewall (WAF) with rules configured to block unauthorized requests to the plugin's administrative API endpoints.

Exploitation Status

Public Exploit Available: No (exploit_available: false)

Analyst Notes: As of July 24, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. Per CISA's SSVC assessment, there is no evidence of active exploitation, and the vulnerability is not considered automatable.

Analyst Recommendation

The high CVSS score underscores the urgency of this remediation. All organizations utilizing the MDJM Event Management plugin must apply the vendor-supplied update immediately to prevent unauthorized privilege escalation and maintain the security of their web environment.

---METADATA---
VENDOR: cascadiawebservices
PRODUCT: MountDev AI MCP Connector for WordPress
AFFECTED_VERSIONS: 0 through 1.6.1
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
The MountDev AI MCP Connector plugin for WordPress contains an authorization bypass flaw that allows unauthenticated attackers to obtain administrative OAuth tokens.

Executive Summary:
An authorization bypass vulnerability in the MountDev AI MCP Connector plugin permits unauthenticated attackers to gain administrative privileges by manipulating the OAuth flow.

Vulnerability Details

CVE-ID: CVE-2026-15015

Affected Software: cascadiawebservices MountDev AI MCP Connector for WordPress

Affected Versions: 0 through 1.6.1

Vulnerability: This vulnerability stems from a failure to verify user authorization during the OAuth process. Unauthenticated attackers can exploit the dynamic client registration endpoint to register malicious clients and subsequently obtain administrator-bound tokens.

Business Impact

This vulnerability grants an attacker full administrative-equivalent access to the WordPress site, including control over user accounts, site configuration, and sensitive content. Given the CVSS score of 9.8, the business impact is extreme, as it effectively nullifies existing authentication controls and allows for total site takeover and data breach.

Remediation Plan

Immediate Action: Update the MountDev AI MCP Connector plugin to version 1.6.2 or later immediately.

Proactive Monitoring: Audit administrative user accounts for suspicious activity or unauthorized account creation that may have occurred during the period the plugin was vulnerable.

Compensating Controls: Ensure that sensitive administrative endpoints are restricted by IP address or secondary authentication mechanisms if they are accessible via the plugin's tool surface.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of July 23, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The design flaw in the OAuth implementation allows for automated exploitation, making it a high-priority target for attackers.

Analyst Recommendation

The risk of unauthorized administrative access is critical. Organizations using the MountDev AI MCP Connector must apply the security update immediately. If patching is delayed, it is highly recommended to disable the plugin to prevent potential exploitation of the vulnerable OAuth endpoints.

---METADATA---
VENDOR: cozyvision1
PRODUCT: SMS Alert – SMS & OTP for WooCommerce
AFFECTED_VERSIONS: 0 through 3.9.7
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
The SMS Alert plugin for WordPress is vulnerable to authentication bypass and account takeover due to an insecure OTP validation process that fails to bind verification status to specific phone numbers.

Executive Summary:
A critical authentication bypass flaw in the SMS Alert plugin for WordPress allows unauthenticated attackers to hijack user accounts, including administrator accounts.

Vulnerability Details

CVE-ID: CVE-2026-15014

Affected Software: cozyvision1 SMS Alert – SMS & OTP for WooCommerce

Affected Versions: 0 through 3.9.7

Vulnerability: The processRegistration() function uses a session flag that is not bound to a specific phone number. Unauthenticated attackers can verify a phone number they control and then substitute the billing_phone parameter to log in as a victim, including administrative users.

Business Impact

The CVSS score of 9.8 highlights the potential for total account takeover. By gaining access to administrative accounts, an attacker can fully compromise the WordPress installation, potentially leading to unauthorized data access, malware distribution, or total site defacement.

Remediation Plan

Immediate Action: Update the SMS Alert plugin to the latest available version immediately to resolve the authentication logic flaw.

Proactive Monitoring: Review user registration logs for anomalies, such as multiple registrations originating from the same IP address or unexpected changes to account phone numbers.

Compensating Controls: Disable user registration on the WordPress site until the plugin is updated, or implement additional secondary authentication factors that are not reliant on the vulnerable plugin.

Exploitation Status

Public Exploit Available: No confirmed public exploit.

Analyst Notes: As of July 28, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. This is a logic flaw that requires minimal technical sophistication to exploit once the underlying issue is understood.

Analyst Recommendation

Due to the critical nature of account takeover vulnerabilities, this issue should be treated with the highest priority. Administrators must update the plugin immediately to protect user accounts and maintain the integrity of their WordPress installation.

---METADATA---
VENDOR: cyberlord92
PRODUCT: SAML Single Sign On – SSO Login
AFFECTED_VERSIONS: 0 through 5.4.3
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
The SAML SSO plugin for WordPress is vulnerable to signature algorithm confusion, allowing unauthenticated attackers to forge assertions and gain administrative access.

Executive Summary:
A critical signature validation flaw in the SAML Single Sign On plugin allows unauthenticated attackers to bypass authentication and achieve full administrator-level account takeover.

Vulnerability Details

CVE-ID: CVE-2026-15013

Affected Software: cyberlord92 SAML Single Sign On – SSO Login

Affected Versions: 0 through 5.4.3

Vulnerability: The plugin incorrectly uses user-provided SAML response data to determine the cryptographic signature algorithm, allowing an attacker to force the use of a weaker or mismatched algorithm. This enables the forging of SAML assertions that the plugin improperly validates, resulting in complete authentication bypass.

Business Impact

This vulnerability carries a CVSS score of 9.8, reflecting the ease of exploitation and the severity of the outcome. An attacker can gain full administrative control over the WordPress instance, leading to total system compromise, data exfiltration, and the ability to inject malicious code into the site.

Remediation Plan

Immediate Action: Update the SAML Single Sign On – SSO Login plugin to the latest available version provided by the vendor.

Proactive Monitoring: Review WordPress access logs for successful logins that did not originate from the expected Identity Provider (IdP) or show signs of unusual authentication parameters.

Compensating Controls: Temporarily disable the SAML SSO functionality if an immediate update is not feasible, forcing users to authenticate through standard WordPress mechanisms.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of July 15, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The vulnerability is highly dangerous due to the reliance on SAML for secure identity verification.

Analyst Recommendation

Given the critical nature of authentication bypass flaws, immediate patching is required. Security teams should prioritize this update to ensure that the SAML implementation remains secure against signature forgery attempts.

---METADATA---
VENDOR: emarket-design
PRODUCT: Customer Support Ticket System & Helpdesk
AFFECTED_VERSIONS: 0 through 6.0.5
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
The Customer Support Ticket System & Helpdesk WordPress plugin is vulnerable to unauthenticated code injection via the path parameter, allowing attackers to invoke arbitrary PHP functions.

Executive Summary:
A critical vulnerability in the Customer Support Ticket System & Helpdesk plugin allows unauthenticated attackers to execute arbitrary code, posing a severe risk to site integrity and data security.

Vulnerability Details

CVE-ID: CVE-2026-15011

Affected Software: emarket-design Customer Support Ticket System & Helpdesk

Affected Versions: 0 through 6.0.5

Vulnerability: This is a code injection vulnerability stemming from insufficient validation of the path parameter. An unauthenticated attacker can trigger dynamic function invocation to execute arbitrary parameterless PHP functions on the target server.

Business Impact

Successful exploitation allows an attacker to manipulate server-side processes, which can lead to full site compromise, unauthorized data exposure, or total service disruption. With a CVSS score of 9.8, this vulnerability represents an extreme risk to business operations and sensitive customer data.

Remediation Plan

Immediate Action: Update the Customer Support Ticket System & Helpdesk plugin to version 6.0.6 or later immediately.

Proactive Monitoring: Review web server access logs for anomalous requests containing path parameters or unexpected function calls.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to block suspicious input patterns targeting plugin-specific parameters until the update is applied.

Exploitation Status

Public Exploit Available: No confirmed public weaponized exploit found in curated databases.

Analyst Notes: As of July 23, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is highly dangerous due to the lack of authentication requirements and the ability to execute arbitrary code.

Analyst Recommendation

Given the critical nature of this vulnerability and the potential for total system compromise, administrators must prioritize updating the plugin to version 6.0.6. Failure to patch leaves the WordPress instance exposed to trivial remote exploitation.

---METADATA---
VENDOR: Uncanny Owl
PRODUCT: Uncanny Automator
AFFECTED_VERSIONS: 0 through 7.3.1.4
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
The Uncanny Automator plugin for WordPress contains a deserialization vulnerability that allows for arbitrary file deletion due to insufficient path validation in the fr_token function.

Executive Summary:
A critical deserialization vulnerability in the Uncanny Automator plugin for WordPress may allow unauthenticated attackers to delete arbitrary files on the server.

Vulnerability Details

CVE-ID: CVE-2026-15008

Affected Software: Uncanny Owl Uncanny Automator

Affected Versions: 0 through 7.3.1.4

Vulnerability: The plugin is vulnerable to improper deserialization (CWE-502) within the fr_token function, which leads to insufficient file path validation. This flaw can be triggered to perform arbitrary file deletion, potentially disrupting site operations.

Business Impact

Successful exploitation of this vulnerability could lead to the deletion of critical system files, potentially causing complete service outages or site instability. The CVSS score of 8.1 reflects the high risk posed to service availability, even though the attack requires specific conditions to trigger.

Remediation Plan

Immediate Action: Update the Uncanny Automator plugin to version 7.4.0 or higher to patch the deserialization and file path validation flaws.

Proactive Monitoring: Monitor server logs for unexpected file deletion attempts or errors related to file access in plugin directories.

Compensating Controls: Utilize a Web Application Firewall (WAF) to filter malicious requests targeting the plugin's integration tokens and endpoints.

Exploitation Status

Public Exploit Available: Unknown.

Analyst Notes: As of July 17, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. While deserialization flaws are often complex to exploit, they represent a significant risk to system integrity.

Analyst Recommendation

The severity of this vulnerability necessitates an immediate update to version 7.4.0. Administrators should prioritize this patch to prevent potential service disruption and ensure the continued stability of the WordPress environment.

---METADATA---
VENDOR: Bitpress
PRODUCT: Bit Integrations
AFFECTED_VERSIONS: 0 through 2.9.0
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
The Bit Integrations plugin for WordPress contains a path traversal vulnerability that could allow unauthenticated attackers to read sensitive files on the server.

Executive Summary:
A directory traversal vulnerability in the Bit Integrations plugin for WordPress allows unauthorized access to sensitive files on the host server.

Vulnerability Details

CVE-ID: CVE-2026-15006

Affected Software: Bit Integrations

Affected Versions: 0 through 2.9.0

Vulnerability: This plugin is vulnerable to directory traversal (CWE-22) via improper limitation of a pathname to a restricted directory, allowing unauthenticated attackers to access arbitrary files on the system.

Business Impact

Successful exploitation of this vulnerability permits unauthorized reading of sensitive configuration files or system data, which often leads to further compromise. With a CVSS score of 7.5, this high-severity flaw threatens the confidentiality of the entire WordPress instance and its underlying server environment.

Remediation Plan

Immediate Action: Update the Bit Integrations plugin to the latest available version provided by the vendor.

Proactive Monitoring: Review web server access logs for requests containing directory traversal sequences, such as dot-dot-slash patterns, directed toward the plugin files.

Compensating Controls: Utilize a Web Application Firewall (WAF) to block requests containing directory traversal payloads, which provides a critical layer of defense while the software is being updated.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of August 1, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherent to improper input validation within the plugin controller logic.

Analyst Recommendation

Path traversal vulnerabilities are frequently targeted for initial reconnaissance and sensitive data extraction. Administrators should prioritize upgrading the Bit Integrations plugin immediately to eliminate the risk of unauthorized file exposure.

---METADATA---
VENDOR: timwhitlock
PRODUCT: Loco Translate
AFFECTED_VERSIONS: 0 through 2.8.5
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
The Loco Translate plugin for WordPress is vulnerable to Cross-Site Request Forgery (CSRF), which may allow an attacker to perform unauthorized actions on behalf of an authenticated administrator.

Executive Summary:
The Loco Translate plugin for WordPress is susceptible to a CSRF vulnerability that could allow an attacker to perform unauthorized actions on the platform.

Vulnerability Details

CVE-ID: CVE-2026-15005

Affected Software: timwhitlock Loco Translate

Affected Versions: 0 through 2.8.5

Vulnerability: This is a CSRF vulnerability (CWE-352) present in the plugin's administrative controllers. An unauthenticated attacker can trick a logged-in administrator into performing unintended actions by enticing them to click a malicious link or visit a crafted website.

Business Impact

The CVSS score of 8.8 highlights the critical nature of this vulnerability, as it allows attackers to bypass intended security controls. If successfully exploited, an attacker could change system settings or execute administrative tasks, potentially leading to site-wide disruption or unauthorized data modifications.

Remediation Plan

Immediate Action: Update the Loco Translate plugin to the latest version beyond 2.8.5 to address the CSRF protection deficiency.

Proactive Monitoring: Monitor site activity logs for unexpected administrative changes or actions occurring during periods where no legitimate administrator is active.

Compensating Controls: Advise administrators to maintain strict browsing habits and utilize browser-based security extensions to mitigate the risk of CSRF attacks.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of July 16, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. CSRF attacks rely on the victim being logged in, which provides a layer of dependency for the attacker.

Analyst Recommendation

Due to the potential for administrative account compromise via CSRF, it is imperative to update the Loco Translate plugin immediately. Administrators should ensure that the plugin is running the latest version to protect against this request forgery vector.

---METADATA---
VENDOR: WordPress
PRODUCT: Autopay (platnosci-online-blue-media)
AFFECTED_VERSIONS: 0 through 5.0.0
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
The Autopay plugin for WordPress is susceptible to Stored Cross-Site Scripting (XSS) due to improper neutralization of user-supplied input, potentially allowing execution of malicious scripts.

Executive Summary:
A Stored Cross-Site Scripting vulnerability in the Autopay plugin for WordPress allows unauthenticated attackers to execute arbitrary scripts in the context of a user session.

Vulnerability Details

CVE-ID: CVE-2026-15002

Affected Software: WordPress Autopay plugin

Affected Versions: 0 through 5.0.0

Vulnerability: This is a Stored Cross-Site Scripting (CWE-79) vulnerability where the plugin fails to sanitize input properly. The vulnerability is exploitable by unauthenticated attackers, as indicated by the CVSS vector's PR:N (Privileges Required: None) attribute.

Business Impact

Successful exploitation allows an attacker to inject malicious scripts into the web application, which can lead to session hijacking, unauthorized actions on behalf of the victim, or the redirection of users to malicious sites. With a CVSS score of 7.2, this vulnerability represents a significant security risk, as it compromises the integrity and confidentiality of the user interface.

Remediation Plan

Immediate Action: Update the Autopay plugin to version 5.0.1 or later to apply the necessary input sanitization patches.

Proactive Monitoring: Review web access logs for unusual traffic patterns or suspicious injection attempts directed at plugin-related files.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block common XSS payloads in incoming requests.

Exploitation Status

Public Exploit Available: Unknown.

Analyst Notes: As of August 16, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous because it allows unauthenticated script injection into the administrative or frontend interfaces.

Analyst Recommendation

Given the high CVSS score and the nature of Stored XSS, administrators should prioritize updating the Autopay plugin immediately. Failure to patch may expose users and administrative sessions to malicious script execution.

---METADATA---
VENDOR: bLoyal
PRODUCT: bLoyal: Loyalty & Promotions by bLoyal
AFFECTED_VERSIONS: up to and including 3.1.611.78
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
The bLoyal: Loyalty & Promotions by bLoyal plugin for WordPress is vulnerable to privilege escalation, allowing authenticated users to elevate their permissions to administrative levels.

Executive Summary:
A critical privilege escalation vulnerability in the bLoyal: Loyalty & Promotions by bLoyal plugin permits authenticated attackers to gain administrative privileges.

Vulnerability Details

CVE-ID: CVE-2026-15001

Affected Software: bLoyal bLoyal: Loyalty & Promotions by bLoyal

Affected Versions: up to and including 3.1.611.78

Vulnerability: This vulnerability (CWE-269) stems from improper privilege management, which allows an authenticated user to perform unauthorized actions and escalate their account privileges within the WordPress environment.

Business Impact

Exploitation of this flaw grants an attacker administrative access, enabling them to exert full control over the website. This results in a total loss of confidentiality, integrity, and availability of the platform, posing a severe risk to business operations and customer data security.

Remediation Plan

Immediate Action: As there is no patch available, the plugin must be deactivated and removed from the environment immediately to prevent exploitation.

Proactive Monitoring: Audit existing user accounts for any unauthorized changes or newly created administrative accounts that may have been established during a period of compromise.

Compensating Controls: Restrict access to the WordPress dashboard and administrative functions via IP whitelisting or additional authentication layers to mitigate the risk of unauthorized privilege escalation.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of August 15, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The absence of a patch necessitates a proactive removal of the vulnerable software to maintain security posture.

Analyst Recommendation

Due to the high severity of privilege escalation, administrators must treat this as an urgent issue and remove the plugin immediately. Re-enable the software only after the vendor has provided a verified security update.

---METADATA---
VENDOR: IBM
PRODUCT: Aspera Faspex 5
AFFECTED_VERSIONS: 5.0.0 through 5.0.15.4
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
IBM Aspera Faspex 5 contains an insufficient session expiration vulnerability that could allow an unauthenticated attacker to hijack active user sessions.

Executive Summary:
IBM Aspera Faspex 5 is vulnerable to session hijacking due to insufficient session expiration, posing a high risk of unauthorized access.

Vulnerability Details

CVE-ID: CVE-2026-14996

Affected Software: IBM Aspera Faspex 5

Affected Versions: 5.0.0 through 5.0.15.4

Vulnerability: The application fails to properly expire user sessions under certain conditions, which corresponds to CWE-613. This flaw allows an unauthenticated attacker to potentially access active sessions without proper authorization.

Business Impact

With a CVSS score of 8.2, this vulnerability represents a significant risk to data confidentiality. Unauthorized access to active sessions could allow an attacker to exfiltrate sensitive files or perform administrative actions within the Aspera Faspex environment.

Remediation Plan

Immediate Action: Upgrade IBM Aspera Faspex to version 5.0.16 or later as specified in the vendor advisory.

Proactive Monitoring: Monitor user session logs for unusual login times, multiple concurrent sessions from different IP addresses for the same user, or suspicious file transfer activity.

Compensating Controls: Implement strict network access controls to limit access to the Faspex interface to trusted IP ranges only.

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of July 29, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The lack of proper session management is a critical oversight that requires immediate attention.

Analyst Recommendation

Organizations utilizing IBM Aspera Faspex must perform the update to version 5.0.16 immediately to ensure session integrity. Regular patching of this platform is essential to prevent unauthorized access to high-value data transfers.

---METADATA---
VENDOR: WP Duplicate
PRODUCT: WP Duplicate Plugin
AFFECTED_VERSIONS: Up to and including 1.1.8
---END_METADATA---

Description Summary:
The WP Duplicate plugin for WordPress allows authenticated subscribers to trigger a chain of vulnerabilities leading to unauthenticated remote code execution via arbitrary file upload.

Executive Summary:
A critical vulnerability chain in the WP Duplicate plugin allows authenticated users to bypass security checks, enabling unauthenticated attackers to upload malicious files and execute code remotely.

Vulnerability Details

CVE-ID: CVE-2026-1499

Affected Software: WP Duplicate Plugin (WordPress)

Affected Versions: Up to and including 1.1.8

Vulnerability: This is a multi-stage flaw involving missing authorization on the process_add_site() AJAX action and path traversal. A subscriber-level attacker can set an internal key, which an unauthenticated attacker can subsequently use to bypass checks in the handle_upload_single_big_file() function, resulting in arbitrary file upload and remote code execution (RCE).

Business Impact

The impact is severe, as it allows low-privileged users to facilitate a full server compromise by unauthenticated external actors. This can lead to website defacement, data exfiltration, or the use of the server as a pivot point for further internal network attacks. The CVSS score of 9.8 is justified by the ease of moving from low-level access to full RCE.

Remediation Plan

Immediate Action: Deactivate and remove the WP Duplicate plugin immediately until a version higher than 1.1.8 is available and verified to contain the fix.

Proactive Monitoring: Review WordPress AJAX logs and check the /wp-content/uploads/ directory for suspicious PHP files or unexpected directory structures.

Compensating Controls: Implement a WAF to block unauthorized AJAX calls and restrict file upload types at the web server level.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of Feb 6, 2026, there is no public information indicating active exploitation. Plugin vulnerabilities involving RCE are frequently exploited by automated botnets shortly after disclosure.

Analyst Recommendation

The complexity of this vulnerability chain does not diminish its risk; rather, it highlights a fundamental failure in the plugin's authorization logic. Organizations running WordPress should immediately update or remove this plugin. Given the potential for unauthenticated RCE, this is a critical priority for any web-facing WordPress installation.

---METADATA---
VENDOR: IBM
PRODUCT: WebSphere Application Server - Liberty
AFFECTED_VERSIONS: 17.0.0.3 through 26.0.0.8
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
IBM WebSphere Application Server Liberty is susceptible to improper privilege management, which could allow a remote attacker to gain unauthorized access via a crafted request.

Executive Summary:
A privilege management vulnerability in IBM WebSphere Application Server Liberty could allow unauthorized users to gain elevated access to the application environment.

Vulnerability Details

CVE-ID: CVE-2026-14980

Affected Software: IBM WebSphere Application Server - Liberty

Affected Versions: 17.0.0.3 through 26.0.0.8

Vulnerability: This vulnerability involves improper privilege management (CWE-269), allowing an attacker to potentially perform unauthorized actions. The attack is network-based and requires user interaction, but it does not require prior authentication to the target application.

Business Impact

Successful exploitation could lead to the compromise of sensitive administrative functions, unauthorized data access, or the manipulation of application workflows. With a CVSS score of 8.3, this vulnerability represents a high risk to application integrity and confidentiality, especially for business-critical services deployed on the Liberty platform.

Remediation Plan

Immediate Action: Apply the available interim fix or fix pack containing the patch for APAR PH71678, as recommended by IBM.

Proactive Monitoring: Monitor application access logs for suspicious patterns, such as requests directed at administrative endpoints or unusual privilege escalation attempts by standard users.

Compensating Controls: Implement a Web Application Firewall (WAF) with rules configured to inspect and block malicious or malformed requests targeting the Liberty collectiveController feature.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of July 31, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. Improper privilege management flaws are frequently targeted by attackers to escalate their footprint within a web application environment.

Analyst Recommendation

Administrators should verify their version of WebSphere Application Server Liberty and apply the necessary patches provided by IBM immediately. Ensuring that security patches are applied is essential to preventing potential unauthorized access to the application server and its hosted services.

---METADATA---
VENDOR: IBM
PRODUCT: WebSphere Application Server
AFFECTED_VERSIONS: 8.5, 9.0
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
IBM WebSphere Application Server is susceptible to a deserialization of untrusted data vulnerability, which could allow an unauthenticated attacker to achieve remote code execution.

Executive Summary:
A critical deserialization vulnerability in IBM WebSphere Application Server could allow unauthenticated attackers to execute arbitrary code.

Vulnerability Details

CVE-ID: CVE-2026-14974

Affected Software: IBM WebSphere Application Server

Affected Versions: 8.5, 9.0

Vulnerability: The application is vulnerable to CWE-502, where it deserializes untrusted data without sufficient validation. This flaw allows an unauthenticated attacker to manipulate serialized objects to perform malicious actions.

Business Impact

The CVSS score of 8.1 highlights the critical nature of this vulnerability. Successful exploitation could lead to a full system compromise, including complete loss of confidentiality, integrity, and availability of the application server.

Remediation Plan

Immediate Action: Apply the interim fix for APAR DT496118 or upgrade to the respective fix pack versions as detailed in the vendor advisory.

Proactive Monitoring: Monitor server memory usage and process creation logs for signs of anomalous activity that might indicate code execution attempts.

Compensating Controls: Utilize a Web Application Firewall to block suspicious serialized objects or known malicious payloads before they reach the application server.

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of July 29, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. Deserialization vulnerabilities are inherently dangerous and often serve as gateways for deeper network penetration.

Analyst Recommendation

Due to the high risk of arbitrary code execution, it is imperative to apply the provided IBM fixes immediately. Security teams should prioritize this update to protect the application server from potential exploitation.

---METADATA---
VENDOR: Bricksforge
PRODUCT: Bricksforge
AFFECTED_VERSIONS: 0 through 3.1.8.6
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
The Bricksforge WordPress plugin contains a privilege escalation vulnerability in the Pro Forms component, allowing unauthenticated attackers to register new administrator accounts.

Executive Summary:
A critical privilege escalation vulnerability in the Bricksforge WordPress plugin allows unauthenticated attackers to create unauthorized administrative accounts, posing a severe risk of total site compromise.

Vulnerability Details

CVE-ID: CVE-2026-14956

Affected Software: Bricksforge Bricksforge

Affected Versions: 0 through 3.1.8.6

Vulnerability: This flaw stems from improper validation of the fieldIds parameter within the Pro Forms registration action. An unauthenticated attacker can manipulate this parameter to inject unauthorized field IDs into the registration process, successfully creating an account with administrative privileges.

Business Impact

The ability for an unauthenticated user to elevate their privileges to administrator level grants them full control over the WordPress installation. This leads to complete data exfiltration, unauthorized content modification, and potential malware distribution. With a CVSS score of 9.8, this vulnerability represents a critical threat to business continuity and data integrity.

Remediation Plan

Immediate Action: Update the Bricksforge plugin to the latest available version immediately to patch the validation logic flaw.

Proactive Monitoring: Review user account creation logs for suspicious or unauthorized administrator registrations.

Compensating Controls: Disable public-facing Pro Forms registration elements until the patch has been applied to prevent exploitation.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of July 16, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous due to its low attack complexity and the lack of required authentication for exploitation.

Analyst Recommendation

Given the critical nature of this privilege escalation vulnerability, administrators must prioritize updating the Bricksforge plugin. Immediate action is required to prevent unauthorized access and potential full system takeover.

---METADATA---
VENDOR: Frauscher
PRODUCT: FDS 102
AFFECTED_VERSIONS: 2.13.0 through 2.13.3
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
The Frauscher FDS 102 system is vulnerable to session hijacking, as administrative session identifiers are inadvertently stored in plaintext within downloadable error log archives.

Executive Summary:
A critical information disclosure vulnerability in Frauscher FDS 102 allows low privileged attackers to hijack active administrative sessions.

Vulnerability Details

CVE-ID: CVE-2026-14948

Affected Software: Frauscher FDS 102

Affected Versions: 2.13.0 through 2.13.3

Vulnerability: This is an information disclosure vulnerability (CWE-532) where sensitive session identifiers are written to log files. A low privileged remote attacker can download these logs to extract active session tokens, bypassing the need for administrative credentials.

Business Impact

Successful exploitation results in complete administrative access to the FDS 102 system. This poses a severe risk to operational security, as an attacker could modify system settings or access sensitive industrial data. The CVSS score of 8.8 highlights the high potential for unauthorized access and lateral movement within the network.

Remediation Plan

Immediate Action: Contact the vendor for specific patch availability and apply all recommended security updates to the FDS 102 system.

Proactive Monitoring: Audit access logs for unauthorized attempts to download diagnostic or error files, particularly by low privileged accounts.

Compensating Controls: Restrict access to diagnostic interfaces and error log downloads to authorized personnel only, utilizing network segmentation to isolate the management interface.

Exploitation Status

Public Exploit Available: No.

Analyst Notes: As of August 20, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The vulnerability is highly exploitable once an attacker gains access to the log files, which are frequently accessible in misconfigured environments.

Analyst Recommendation

This vulnerability represents a significant security oversight that directly compromises the authentication mechanism. Users must prioritize obtaining and installing the vendor-supplied fix to prevent unauthorized administrative control.

---METADATA---
VENDOR: Unknown
PRODUCT: Password Protected — Lock Entire Site, Pages, Posts, Categories, and Partial Content
AFFECTED_VERSIONS: Password Protected — Lock Entire Site, Pages, Posts, Categories, and Partial Content WordPress plugin versions 2.6.8 through 2.8.3
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
The Password Protected WordPress plugin fails to restrict REST API access, allowing unauthenticated users to bypass sitewide password protection and read protected content.

Executive Summary:
A regression in the Password Protected WordPress plugin allows unauthenticated users to bypass site security and access restricted content via the REST API.

Vulnerability Details

CVE-ID: CVE-2026-14943

Affected Software: Password Protected — Lock Entire Site, Pages, Posts, Categories, and Partial Content

Affected Versions: 2.6.8 through 2.8.3

Vulnerability: This is a regression of a previously patched vulnerability. The plugin fails to properly enforce authorization checks on the REST API when specific options are enabled, permitting unauthenticated visitors to bypass the password gate and access protected pages and account identifiers.

Business Impact

This vulnerability carries a CVSS score of 7.5, indicating a high risk of unauthorized information disclosure. Successful exploitation allows unauthorized parties to bypass access controls intended to protect private or sensitive business content, potentially leading to data leaks and reputational damage.

Remediation Plan

Immediate Action: Update the Password Protected plugin to version 2.8.4 or later immediately.

Proactive Monitoring: Review access logs for unusual patterns of REST API requests, specifically those originating from unauthenticated sessions targeting protected content.

Compensating Controls: Temporarily disable the plugin or restrict access to the WordPress REST API via WAF rules until the patch can be applied.

Exploitation Status

Public Exploit Available: Unknown.

Analyst Notes: As of August 14, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is easily triggered by any unauthenticated user with access to the REST API endpoints.

Analyst Recommendation

The recurrence of this vulnerability in a security-focused plugin is significant. Administrators must apply the update to version 2.8.4 immediately to restore the integrity of the site's access control mechanisms and prevent unauthorized exposure of sensitive content.

---METADATA---
VENDOR: Google Cloud
PRODUCT: BigQuery, Dataform, Colab Enterprise
AFFECTED_VERSIONS: 2025-10 up to (excluding) 2026-05-10
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
Google Cloud BigQuery, Dataform, and Colab Enterprise contained a missing authorization vulnerability that allowed authenticated attackers to perform cross-tenant repository takeovers.

Executive Summary:
A now-patched missing authorization vulnerability in Google Cloud services allowed authenticated users to escalate privileges and access unauthorized cross-tenant repositories.

Vulnerability Details

CVE-ID: CVE-2026-14934

Affected Software: Google Cloud BigQuery, Dataform, and Colab Enterprise

Affected Versions: 2025-10 up to (excluding) 2026-05-10

Vulnerability: This vulnerability involved missing authorization (CWE-862) within the repository creation functionality. An authenticated user could exploit this flaw to perform unauthorized actions across different tenant environments, effectively bypassing standard cloud isolation boundaries.

Business Impact

The impact of this vulnerability was severe (CVSS 9.4), as it allowed for cross-tenant data access and unauthorized repository takeover. This could have resulted in the exposure of highly sensitive proprietary data or source code, potentially affecting multiple organizations utilizing these Google Cloud services simultaneously.

Remediation Plan

Immediate Action: No customer action is required as Google Cloud has already implemented the necessary patches on the backend.

Proactive Monitoring: Review audit logs for the period between October 2025 and May 10, 2026, for any anomalous repository creation or access events that may indicate prior exploitation.

Compensating Controls: While the vulnerability is patched, maintain standard IAM (Identity and Access Management) best practices, such as the Principle of Least Privilege, to limit the potential impact of any future authorization flaws.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of July 13, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The issue was addressed by the vendor on the backend, effectively neutralizing the risk for all customers.

Analyst Recommendation

This issue is resolved. Security teams should focus on reviewing historical audit logs if they suspect their environment was targeted during the affected timeframe. No further software remediation is required for this specific vulnerability.

---METADATA---
VENDOR: WordPress
PRODUCT: JS Help Desk
AFFECTED_VERSIONS: 0 up to (excluding) 3.1.4
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
The JS Help Desk WordPress plugin contains a missing authorization vulnerability that allows unauthenticated attackers to access sensitive information.

Executive Summary:
A missing authorization vulnerability in the JS Help Desk WordPress plugin allows unauthenticated attackers to potentially exfiltrate sensitive data.

Vulnerability Details

CVE-ID: CVE-2026-14930

Affected Software: WordPress JS Help Desk

Affected Versions: 0 up to (excluding) 3.1.4

Vulnerability: This vulnerability is a missing authorization flaw (CWE-862). It permits unauthenticated attackers to perform unauthorized actions or access restricted data due to the lack of proper capability checks within the plugin.

Business Impact

The flaw carries a CVSS score of 7.5, indicating a high severity risk. Successful exploitation could lead to the exposure of sensitive help desk data, resulting in privacy violations, potential regulatory non-compliance, and loss of customer trust.

Remediation Plan

Immediate Action: Update the JS Help Desk plugin to version 3.1.4 or later immediately.

Proactive Monitoring: Review web server access logs for unusual request patterns targeting plugin-specific endpoints or unauthorized data retrieval attempts.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules designed to detect and block unauthorized access attempts targeting WordPress plugin vulnerabilities.

Exploitation Status

Public Exploit Available: No (exploit_available: false)

Analyst Notes: As of August 1, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The nature of this flaw makes it highly accessible to remote, unauthenticated actors.

Analyst Recommendation

Given the high severity and the availability of a proof-of-concept, administrators should prioritize updating the JS Help Desk plugin. If an immediate update is not feasible, consider disabling the plugin until a secure version is deployed to mitigate the risk of unauthorized data exposure.

---METADATA---
VENDOR: Tablesome
PRODUCT: Tablesome Table
AFFECTED_VERSIONS: Tablesome Table WordPress plugin before 1.1.31
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
The Tablesome Table WordPress plugin fails to validate authentication for AJAX actions, allowing unauthenticated users to create or overwrite site content.

Executive Summary:
An unauthenticated remote code execution or content manipulation vulnerability in the Tablesome Table WordPress plugin poses a severe risk to site integrity.

Vulnerability Details

CVE-ID: CVE-2026-14924

Affected Software: Tablesome Tablesome Table

Affected Versions: Tablesome Table WordPress plugin before 1.1.31

Vulnerability: This is a Missing Authorization (CWE-862) flaw where the plugin lacks authentication, capability, and nonce checks on specific AJAX actions. An unauthenticated attacker can leverage this to create new published posts or overwrite existing pages on the target WordPress site.

Business Impact

The vulnerability carries a CVSS score of 7.5, indicating a high severity risk. Successful exploitation allows unauthorized individuals to modify website content, which can be used to inject malicious scripts, deface the site, or perform phishing attacks, leading to significant reputational damage and potential loss of user trust.

Remediation Plan

Immediate Action: Update the Tablesome Table WordPress plugin to version 1.1.31 or later immediately.

Proactive Monitoring: Review web server access logs for unusual POST requests directed at plugin-specific AJAX endpoints.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to block unauthorized requests to the plugin's AJAX interface.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of July 28, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The lack of authorization checks makes this flaw trivial to exploit for any remote, unauthenticated user.

Analyst Recommendation

Given the ease of exploitation and the potential for full content control, immediate remediation is required. Administrators must prioritize the update to version 1.1.31 to eliminate this authorization bypass and secure the site against unauthorized content manipulation.

---METADATA---
VENDOR: RegistrationMagic
PRODUCT: User Registration & Membership (WordPress Plugin)
AFFECTED_VERSIONS: Up to, and including, 5.1.2
---END_METADATA---

Description Summary:
The RegistrationMagic WordPress plugin allows unauthenticated attackers to create administrator accounts by exploiting improper privilege management during the membership registration process.

Executive Summary:
A critical privilege management flaw in the RegistrationMagic WordPress plugin allows unauthenticated attackers to register new accounts with full administrative privileges.

Vulnerability Details

CVE-ID: CVE-2026-1492

Affected Software: User Registration & Membership – Custom Registration Form Builder (RegistrationMagic)

Affected Versions: Up to, and including, 5.1.2

Vulnerability: The plugin fails to enforce a server-side allowlist for user roles during registration. This allows an unauthenticated attacker to supply a "role" parameter (e.g., 'administrator') during the registration process, which the plugin accepts and applies to the new account.

Business Impact

This vulnerability results in a total site takeover by allowing any visitor to create an admin account. With a CVSS score of 9.8, the impact is severe, as it bypasses all standard security controls and grants the attacker full access to the WordPress dashboard and underlying data.

Remediation Plan

Immediate Action: Update the RegistrationMagic plugin to the latest version (above 5.1.2) immediately. Verify that the registration settings do not allow role selection by the user.

Proactive Monitoring: Review the WordPress user list for any unauthorized accounts with the 'Administrator' role created recently.

Compensating Controls: Disable public user registration if it is not required for business operations, or implement a manual approval process for all new registrations.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of Mar 3, 2026, there is no public information indicating active exploitation. This type of vulnerability is easily exploitable via automated scripts, making rapid remediation essential.

Analyst Recommendation

The ability for unauthenticated users to grant themselves administrative rights is a critical security failure. Immediate patching is mandatory to protect the integrity of the WordPress site and the privacy of its users.

---METADATA---
VENDOR: ShopMonitor.io
PRODUCT: ShopMonitor.io WordPress Plugin
AFFECTED_VERSIONS: Versions before 1.2.0
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A critical authentication bypass in the ShopMonitor.io WordPress plugin allows unauthenticated attackers to hijack administrator accounts via email redirection.

Executive Summary:
The ShopMonitor.io WordPress plugin contains an authentication bypass vulnerability that permits attackers to perform full account takeover of the WordPress administrator.

Vulnerability Details

CVE-ID: CVE-2026-14919

Affected Software: ShopMonitor.io WordPress Plugin

Affected Versions: Versions before 1.2.0

Vulnerability: The plugin fails to perform proper capability checks on its email-rerouting test mode. An unauthenticated attacker can manipulate request headers to satisfy internal checks, allowing them to redirect critical emails, such as password reset links, to an attacker-controlled address.

Business Impact

This vulnerability enables total account takeover of the WordPress administrator, leading to full site compromise and potential data exfiltration. Given the critical 9.8 CVSS score, the impact is severe, as it bypasses the primary authentication mechanism of the entire WordPress installation.

Remediation Plan

Immediate Action: Update the ShopMonitor.io plugin to version 1.2.0 or higher immediately.

Proactive Monitoring: Review WordPress user account logs for unexpected password reset requests or unauthorized account modifications.

Compensating Controls: If an update cannot be applied immediately, deactivate the ShopMonitor.io plugin entirely to remove the attack vector.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of July 31, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous due to its ability to facilitate administrative account takeover without requiring prior credentials.

Analyst Recommendation

This vulnerability represents a direct threat to the integrity of the WordPress site. Administrators must verify their plugin version and apply the update to 1.2.0 immediately, or deactivate the plugin if the update is not currently feasible, to prevent unauthorized account takeovers.

---METADATA---
VENDOR: StylemixThemes
PRODUCT: Cost Calculator Builder PRO
AFFECTED_VERSIONS: 0 through 4.0.3
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
The Cost Calculator Builder PRO plugin for WordPress is vulnerable to remote code execution via insufficient sanitization of input passed to a PHP eval function.

Executive Summary:
A critical remote code execution vulnerability in the StylemixThemes Cost Calculator Builder PRO plugin allows unauthenticated attackers to compromise the server.

Vulnerability Details

CVE-ID: CVE-2026-14900

Affected Software: StylemixThemes Cost Calculator Builder PRO

Affected Versions: 0 through 4.0.3

Vulnerability: This flaw involves improper control of code generation, specifically CWE-94, where malicious input is passed to a PHP eval() function. Although the plugin utilizes a nonce for authentication, the required token is publicly available on front-end pages, effectively allowing unauthenticated exploitation.

Business Impact

The ability for an unauthenticated attacker to execute arbitrary code on the underlying server represents a total compromise of the application and potentially the entire hosting environment. With a CVSS score of 9.8, this vulnerability poses an extreme risk, including data theft, unauthorized modification of site content, and potential lateral movement within the network.

Remediation Plan

Immediate Action: Update the StylemixThemes Cost Calculator Builder PRO plugin to version 4.0.4 or higher immediately.

Proactive Monitoring: Monitor server logs for anomalous PHP execution patterns and inspect the site for any unauthorized files or modified configuration settings.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules designed to detect and block malicious payloads targeting PHP eval() functions or known plugin exploit signatures.

Exploitation Status

Public Exploit Available: No (exploit_available: false)

Analyst Notes: As of Jul 29, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous due to the ease of bypassing the nonce authentication mechanism.

Analyst Recommendation

Given the critical nature of this vulnerability and the ease of exploitation, immediate action is required. Organizations using this plugin must prioritize the update to version 4.0.4 to prevent potential full-system compromise.

---METADATA---
VENDOR: CleanTalk
PRODUCT: Spam protection, Anti-Spam, FireWall plugin
AFFECTED_VERSIONS: All versions up to, and including, 6.71
---END_METADATA---

Description Summary:
The CleanTalk Anti-Spam plugin for WordPress allows unauthenticated attackers to install arbitrary plugins via PTR record spoofing, potentially leading to remote code execution.

Executive Summary:
A critical vulnerability in the CleanTalk Anti-Spam WordPress plugin allows unauthenticated attackers to bypass authorization and install arbitrary plugins, potentially leading to full site takeover via remote code execution.

Vulnerability Details

CVE-ID: CVE-2026-1490

Affected Software: CleanTalk Spam protection, Anti-Spam, FireWall

Affected Versions: All versions up to, and including, 6.71

Vulnerability: This vulnerability involves an authorization bypass in the checkWithoutToken function. By spoofing reverse DNS (PTR) records, an unauthenticated attacker can trick the plugin into allowing unauthorized arbitrary plugin installation and activation, particularly on sites with invalid API keys.

Business Impact

A successful exploit could lead to complete compromise of the WordPress environment. By installing and activating additional vulnerable plugins, attackers can achieve remote code execution (RCE), resulting in data theft, site defacement, and total loss of administrative control. The CVSS score of 9.8 reflects the critical nature of this unauthenticated entry point and the potential for total system impact.

Remediation Plan

Immediate Action: Update the CleanTalk Anti-Spam plugin to the latest available version (6.72 or higher) immediately to patch the vulnerable function.

Proactive Monitoring: Review WordPress audit logs for any unauthorized plugin installations or activations and verify the validity of your CleanTalk API keys.

Compensating Controls: Implement a Web Application Firewall (WAF) to filter suspicious traffic and restrict unauthorized administrative actions at the network edge.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of Feb 15, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the critical CVSS score and the ability for unauthenticated attackers to trigger RCE, the potential for exploitation is extremely high.

Analyst Recommendation

This vulnerability represents a severe risk to WordPress integrity. Organizations must prioritize the update of the CleanTalk plugin to the latest version immediately. Failure to remediate this flaw could allow an external actor to gain full administrative access and execute malicious code without any prior credentials.

---METADATA---
VENDOR: BAKERSCOT
PRODUCT: String::Util
AFFECTED_VERSIONS: String::Util versions before 1.36 for Perl
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A regular expression denial of service (ReDoS) vulnerability in the trim and rtrim functions of the String::Util Perl module allows for CPU exhaustion via maliciously crafted inputs.

Executive Summary:
The String::Util Perl module is vulnerable to a regular expression denial of service (ReDoS) attack that can lead to significant resource exhaustion.

Vulnerability Details

CVE-ID: CVE-2026-14895

Affected Software: BAKERSCOT String::Util

Affected Versions: String::Util versions before 1.36 for Perl

Vulnerability: This vulnerability is a regular expression denial of service (ReDoS) due to inefficient regular expression complexity (CWE-1333). Any caller that passes untrusted input to the trim or rtrim functions can trigger CPU exhaustion with a string containing a long run of whitespace. The attack vector is unauthenticated.

Business Impact

The vulnerability carries a CVSS score of 7.5, classifying it as High severity. Successful exploitation results in a denial-of-service condition, which can render applications utilizing this library unresponsive or cause system-wide instability. This could lead to service downtime and potentially impact business continuity for applications relying on this utility for input sanitization.

Remediation Plan

Immediate Action: Upgrade to version 1.36 or later immediately to incorporate the patch that resolves the inefficient regular expression complexity.

Proactive Monitoring: Monitor server CPU utilization and error logs for patterns indicative of resource exhaustion or abnormal processing times during input parsing.

Compensating Controls: Implement input length validation and rate limiting at the application gateway or firewall level to prevent excessively large or complex strings from reaching the vulnerable functions.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of Jul 7, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

The vulnerability represents a clear risk to service availability. Administrators should prioritize upgrading to version 1.36 to eliminate the underlying regex inefficiency. Given the ease with which ReDoS can be triggered, timely patching is essential to ensure system stability.

---METADATA---
VENDOR: WebRehab
PRODUCT: Super Forms – Drag & Drop Form Builder
AFFECTED_VERSIONS: 0 through 6.3.313
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
The Super Forms plugin for WordPress suffers from an unauthenticated arbitrary file upload vulnerability via the submit_form AJAX handler, enabling potential remote code execution.

Executive Summary:
A critical arbitrary file upload vulnerability in the WebRehab Super Forms plugin enables unauthenticated attackers to execute arbitrary code on the underlying WordPress server.

Vulnerability Details

CVE-ID: CVE-2026-14894

Affected Software: WebRehab Super Forms – Drag & Drop Form Builder

Affected Versions: 0 through 6.3.313

Vulnerability: The submit_form function lacks both file type validation and capability checks. Furthermore, the nonce requirement is easily bypassed by unauthenticated visitors using a separate nopriv AJAX endpoint to mint valid session cookies, reducing the attack to two simple HTTP requests.

Business Impact

This vulnerability provides an unauthenticated attacker with a direct path to server-level compromise. By uploading executable files, an attacker can gain persistent access, manipulate site databases, or use the server as a pivot point for lateral movement within the network. The CVSS score of 9.8 reflects the high probability of successful exploitation and the total impact on the application's security posture.

Remediation Plan

Immediate Action: Update the Super Forms – Drag & Drop Form Builder plugin to the latest version immediately to enforce proper nonce validation and file type restrictions.

Proactive Monitoring: Review web server logs for suspicious requests to nopriv AJAX endpoints and unexpected file uploads in the plugin’s directory or the WordPress media library.

Compensating Controls: Implement WAF rules to intercept and block file upload attempts that do not originate from authenticated user sessions or that contain suspicious file extensions.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of Jul 9, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

This vulnerability is highly dangerous due to the trivial nature of the exploit chain. Organizations using this plugin must verify their current version and apply the vendor-provided security update without delay to mitigate the risk of full system compromise.

---METADATA---
VENDOR: HashiCorp
PRODUCT: Nomad
AFFECTED_VERSIONS: 0.4.1 up to (excluding) 2.0.4
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A sandbox escape vulnerability in the HashiCorp Nomad Docker task driver allows job submitters to bind-mount host paths, enabling unauthorized read/write access to the host filesystem.

Executive Summary:
A high-severity sandbox escape in the HashiCorp Nomad Docker task driver allows privileged users to bypass file access restrictions and compromise the host system.

Vulnerability Details

CVE-ID: CVE-2026-14891

Affected Software: HashiCorp Nomad / Nomad Enterprise

Affected Versions: 0.4.1 up to (excluding) 2.0.4

Vulnerability: This vulnerability, identified as an improper link resolution issue, allows a job submitter to bind-mount a host path into a container even when such actions are disabled. The attacker must possess high-level privileges to submit jobs to the cluster.

Business Impact

Successful exploitation allows an attacker to read or modify files on the host machine, effectively breaking the isolation layer between the container and the underlying infrastructure. With a CVSS score of 8.7, this vulnerability represents a severe threat to the security of containerized environments and the underlying host nodes.

Remediation Plan

Immediate Action: Upgrade HashiCorp Nomad and Nomad Enterprise to version 2.0.4 or later immediately.

Proactive Monitoring: Review audit logs for unusual job submissions or attempts to access restricted host paths via the Docker task driver.

Compensating Controls: Implement strict Role-Based Access Control (RBAC) to limit which users can submit jobs to the Nomad cluster, thereby reducing the attack surface.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of July 9, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Given the potential for complete host compromise, upgrading to the patched version is the only effective mitigation. Security teams should treat this as an urgent infrastructure update to maintain the integrity of the Nomad cluster.

---METADATA---
VENDOR: HashiCorp
PRODUCT: Vault Enterprise
AFFECTED_VERSIONS: 2.0.0 up to (excluding) 2.0.4
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
HashiCorp Vault Enterprise is vulnerable to a cross-namespace authorization bypass that allows authenticated users to delete entity storage backing in unauthorized namespaces.

Executive Summary:
A high-severity authorization bypass in HashiCorp Vault Enterprise allows authenticated users to perform unauthorized deletions of entity storage across namespace boundaries.

Vulnerability Details

CVE-ID: CVE-2026-14886

Affected Software: HashiCorp Vault Enterprise

Affected Versions: 2.0.0 up to (excluding) 2.0.4

Vulnerability: This is a missing authorization flaw (CWE-862) occurring within the identity entity batch-delete endpoint. An authenticated caller with permissions in one namespace can manipulate requests to delete critical identity data in separate, restricted namespaces.

Business Impact

Successful exploitation results in the permanent loss of identity storage, which can lead to significant service disruption and denial of service for dependent applications. Given the CVSS score of 8.2, this vulnerability poses a high risk to organizational data integrity and availability, potentially causing widespread operational impact if identity entities are purged.

Remediation Plan

Immediate Action: Update HashiCorp Vault Enterprise to version 2.0.4 or later to resolve the authorization logic flaw.

Proactive Monitoring: Review Vault access and audit logs for unusual batch-delete operations or unexpected administrative activity across namespace boundaries.

Compensating Controls: Restrict access to the identity entity batch-delete endpoint through granular Role-Based Access Control policies until patches are applied.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of August 11, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous due to its impact on storage integrity and the potential for cross-namespace escalation.

Analyst Recommendation

The severity of this flaw necessitates immediate attention. Administrators must prioritize updating Vault Enterprise to the latest version to prevent unauthorized data loss and ensure that administrative actions remain confined to their intended scopes.

---METADATA---
VENDOR: MongoDB
PRODUCT: MongoDB Compass
AFFECTED_VERSIONS: 1.38.0 up to (excluding) 1.49.7
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A vulnerability in MongoDB Compass allows users to override connection options during the import process, potentially leading to OS command injection.

Executive Summary:
A critical OS command injection vulnerability in MongoDB Compass allows attackers to execute arbitrary commands by manipulating connection import options.

Vulnerability Details

CVE-ID: CVE-2026-14881

Affected Software: MongoDB MongoDB Compass

Affected Versions: 1.38.0 up to (excluding) 1.49.7

Vulnerability: This vulnerability is an OS command injection flaw (CWE-78) triggered when importing connection files. The application fails to properly neutralize special elements, allowing an attacker to override restricted connection parameters and execute unauthorized commands on the host system.

Business Impact

Successful exploitation of this vulnerability could allow an attacker to gain full control over the host running MongoDB Compass. Given the CVSS score of 7.8, this poses a significant risk to the integrity and availability of local development environments and potentially connected infrastructure. Unauthorized command execution may lead to data exfiltration or the installation of persistent malicious software.

Remediation Plan

Immediate Action: Update MongoDB Compass to version 1.49.7 or later immediately to apply the vendor-provided patch.

Proactive Monitoring: Review system logs for unusual process creation or unauthorized command-line arguments originating from the MongoDB Compass application.

Compensating Controls: Restrict the ability of users to import external connection configuration files from untrusted sources until the software has been updated.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of July 24, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. While exploitation is not currently observed, the nature of the flaw makes it highly dangerous if an attacker can convince a user to import a malicious configuration file.

Analyst Recommendation

The severity of this command injection vulnerability necessitates immediate action. Administrators and developers should prioritize updating all instances of MongoDB Compass to version 1.49.7 to prevent potential system compromise and unauthorized remote code execution.

---METADATA---
VENDOR: osTicket
PRODUCT: osTicket
AFFECTED_VERSIONS: v1.18.3, v1.17.7
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
osTicket suffers from an incorrect authorization vulnerability that may allow authenticated users to perform unauthorized actions.

Executive Summary:
osTicket is affected by an incorrect authorization flaw that could allow authenticated users to perform actions exceeding their intended permissions.

Vulnerability Details

CVE-ID: CVE-2026-14871

Affected Software: osTicket

Affected Versions: v1.18.3, v1.17.7

Vulnerability: This vulnerability involves incorrect authorization (CWE-863) within the osTicket application. It requires the attacker to be an authenticated user, who can then bypass permission checks to perform unauthorized operations.

Business Impact

An authorization bypass can lead to unauthorized data modification, privilege escalation, or access to sensitive support tickets and customer information. Given the CVSS score of 7.1, this represents a high risk to the integrity and confidentiality of the helpdesk system, which often holds sensitive client communication.

Remediation Plan

Immediate Action: Update osTicket to version 1.18.4 or 1.17.8 immediately to resolve the authorization logic error.

Proactive Monitoring: Review audit logs for unexpected administrative actions or modifications performed by standard user accounts.

Compensating Controls: Implement strict role-based access control policies and review user permissions to ensure that only authorized personnel have access to sensitive helpdesk functions.

Exploitation Status

Public Exploit Available: Yes, a public proof-of-concept exists on GitHub.

Analyst Notes: As of July 19, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The presence of a public proof-of-concept repository increases the likelihood of opportunistic exploitation.

Analyst Recommendation

Due to the availability of a public proof-of-concept and the high severity score, osTicket administrators should apply the provided patches in versions 1.18.4 or 1.17.8 without delay. Failure to update leaves the system exposed to potential unauthorized actions by malicious internal or compromised external users.

---METADATA---
VENDOR: HashiCorp
PRODUCT: Terraform MCP Server
AFFECTED_VERSIONS: 0.3.0 up to (excluding) 1.1.0
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A Server-Side Request Forgery (SSRF) vulnerability exists in the HashiCorp Terraform MCP Server, allowing remote attackers to send unauthorized requests to internal resources.

Executive Summary:
A critical SSRF vulnerability in HashiCorp Terraform MCP Server exposes internal network infrastructure to unauthorized request manipulation.

Vulnerability Details

CVE-ID: CVE-2026-14869

Affected Software: HashiCorp Terraform MCP Server

Affected Versions: 0.3.0 up to (excluding) 1.1.0

Vulnerability: The application is vulnerable to Server-Side Request Forgery (SSRF), allowing an unauthenticated attacker to manipulate the server into making requests to unauthorized or internal network locations.

Business Impact

SSRF vulnerabilities can be used to bypass internal firewalls, scan internal networks, or interact with sensitive metadata services. With a CVSS score of 8.6, the risk of lateral movement or information disclosure within the environment is high.

Remediation Plan

Immediate Action: Upgrade to version 1.1.0 or later as recommended by HashiCorp to mitigate this SSRF risk.

Proactive Monitoring: Monitor server outbound traffic for connections to internal IP ranges or services that the Terraform MCP Server should not be accessing.

Compensating Controls: Implement strict egress filtering on the server to prevent it from initiating requests to sensitive internal endpoints or metadata services.

Exploitation Status

Public Exploit Available: Unknown.

Analyst Notes: As of July 29, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. Per CISA's SSVC assessment, there is no confirmed active exploitation in the wild.

Analyst Recommendation

Organizations should prioritize the update to version 1.1.0 to ensure the vulnerability is fully remediated. Given the potential for internal network discovery and unauthorized access, immediate patching is recommended to secure the environment against potential SSRF exploitation.

---METADATA---
VENDOR: ARC Informatique
PRODUCT: PcVue
AFFECTED_VERSIONS: All versions prior to 17.0.0
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
PcVue projects utilize an inadequate encryption algorithm to protect user account configurations stored in the built-in user directory, affecting all versions prior to 17.

Executive Summary:
Weak encryption used for user account configurations in PcVue (prior to version 17) allows for the potential compromise of sensitive authentication data.

Vulnerability Details

CVE-ID: CVE-2026-14868

Affected Software: ARC Informatique PcVue

Affected Versions: All versions prior to 17.0.0

Vulnerability: This vulnerability involves inadequate encryption strength (CWE-326) within the user directory of PcVue projects. The flaw requires an authenticated user with local access to exploit the weak protection of stored account configurations.

Business Impact

The ability for an attacker to decrypt or manipulate user account configurations poses a severe risk to organizational security, potentially leading to unauthorized access, privilege escalation, or full system compromise. With a CVSS score of 8.4, this vulnerability represents a significant threat to industrial and control environments where account integrity is paramount.

Remediation Plan

Immediate Action: Upgrade to version 17.0.0 or later to ensure the implementation of stronger encryption standards for user directory storage.

Proactive Monitoring: Monitor for unauthorized attempts to access or modify local project configuration files and review user access logs for suspicious activity.

Compensating Controls: Isolate control system networks behind firewalls, disable unnecessary remote access, and ensure that only authorized personnel have physical or local access to the systems.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of July 8, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Organizations relying on older versions of PcVue must treat this as a critical security update. Upgrading to version 17.0.0 is the only effective way to remediate the underlying cryptographic weakness and protect user credentials from unauthorized access.

---METADATA---
VENDOR: FileRun
PRODUCT: FileRun
AFFECTED_VERSIONS: 0 through 2026.2.0
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
An OS command injection vulnerability in FileRun allows authenticated users to execute arbitrary commands on the underlying host system via crafted thumbnail generation requests.

Executive Summary:
FileRun is vulnerable to OS command injection, which allows an authenticated attacker to execute arbitrary system commands and gain unauthorized control over the server.

Vulnerability Details

CVE-ID: CVE-2026-14863

Affected Software: FileRun

Affected Versions: 0 through 2026.2.0

Vulnerability: This vulnerability is a CWE-78 OS command injection flaw occurring during the thumbnail generation process. While the attack requires the attacker to be authenticated (PR:L), the ability to execute system commands results in a high-severity impact on the confidentiality, integrity, and availability of the host server.

Business Impact

A successful exploit grants the attacker the ability to run commands with the privileges of the web application service. This could lead to a full server compromise, data exfiltration, or the installation of persistent malicious backdoors. The CVSS score of 8.8 reflects the high risk posed to the server infrastructure.

Remediation Plan

Immediate Action: Upgrade your FileRun installation to version 2026.2.1 or later to resolve the command injection flaw.

Proactive Monitoring: Audit server logs for suspicious command execution patterns or unauthorized file access attempts originating from the web application user account.

Compensating Controls: Implement a Web Application Firewall (WAF) with rules designed to detect and block command injection attempts, and ensure the FileRun application runs with the least privilege necessary on the host operating system.

Exploitation Status

Public Exploit Available: No (exploit_available: false)

Analyst Notes: As of August 12, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The vulnerability is inherently dangerous because it allows direct interaction with the underlying OS.

Analyst Recommendation

The severity of this command injection vulnerability necessitates an immediate update to version 2026.2.1. System administrators should verify the integrity of their environments following the update to ensure no unauthorized persistence mechanisms were established prior to patching.

---METADATA---
VENDOR: Lenze
PRODUCT: c430, c520, c550, i950 GenA, i950 GenB
AFFECTED_VERSIONS: Lenze c430/c520/c550: 1.0.0 to 1.15.1; i950 GenA: 1.0.0 to 1.14.1; i950 GenB: 2.0.0 to 2.0.2
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
Multiple Lenze products contain an improper signature verification vulnerability in their SSH enablement mechanism, potentially allowing unauthorized access or modification.

Executive Summary:
A high-severity cryptographic signature verification flaw in multiple Lenze industrial controllers may allow local attackers to bypass security controls.

Vulnerability Details

CVE-ID: CVE-2026-14837

Affected Software: Lenze c430, c520, c550, i950 GenA, and i950 GenB

Affected Versions: Lenze c430/c520/c550: 1.0.0 to 1.15.1; i950 GenA: 1.0.0 to 1.14.1; i950 GenB: 2.0.0 to 2.0.2

Vulnerability: This vulnerability (CWE-347) involves an improper verification of cryptographic signatures within the SSH enablement process. The vulnerability requires a local attacker with low privileges to exploit, potentially leading to significant impact on confidentiality, integrity, and availability.

Business Impact

Successful exploitation of this flaw could allow an attacker to bypass authentication or execute unauthorized commands via the SSH mechanism. Given the CVSS score of 7.8, this represents a high-risk scenario for industrial environments, where unauthorized control over hardware could lead to operational disruption, safety hazards, or damage to proprietary physical processes.

Remediation Plan

Immediate Action: Update the affected Lenze firmware to version 1.15.2 (for c430, c520, c550), 1.14.2 (for i950 GenA), or 2.0.3 (for i950 GenB) as specified in the vendor advisory.

Proactive Monitoring: Monitor system access logs for unusual SSH authentication activity or attempts to interact with the SSH enablement service.

Compensating Controls: Restrict physical access to the affected hardware and disable SSH access if it is not required for daily operations.

Exploitation Status

Public Exploit Available: Unknown.

Analyst Notes: As of July 27, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is rooted in the fundamental handling of cryptographic signatures, which poses a substantial risk if an attacker achieves local access to the management interface.

Analyst Recommendation

The vulnerability presents a high risk to the integrity of Lenze industrial hardware. Administrators should prioritize the deployment of the provided firmware updates during the next scheduled maintenance window to ensure that cryptographic protections are properly enforced.

---METADATA---
VENDOR: WordPress
PRODUCT: FlxWoo
AFFECTED_VERSIONS: 0 up to 3.1.1
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
The FlxWoo WordPress plugin before 3.1.1 is affected by an improper authentication vulnerability, allowing unauthenticated attackers to potentially perform unauthorized actions.

Executive Summary:
An improper authentication vulnerability in the FlxWoo WordPress plugin allows unauthenticated attackers to bypass security checks and perform unauthorized operations.

Vulnerability Details

CVE-ID: CVE-2026-14830

Affected Software: WordPress FlxWoo

Affected Versions: 0 up to 3.1.1

Vulnerability: The plugin suffers from an improper authentication flaw (CWE-287), which fails to properly verify user identity, allowing unauthenticated remote attackers to execute unauthorized actions within the scope of the plugin.

Business Impact

Exploitation of this vulnerability could lead to unauthorized modifications of site content or data, potentially impacting the functionality of the associated WooCommerce environment. The CVSS score of 7.5 highlights a high risk that could lead to significant operational disruption if exploited.

Remediation Plan

Immediate Action: Update the FlxWoo plugin to version 3.1.1 or later to resolve the authentication bypass issue.

Proactive Monitoring: Review application logs for unauthorized API calls or unexpected modifications to store settings that occur without legitimate administrative intervention.

Compensating Controls: Implement strict WAF rules to filter requests to the FlxWoo plugin endpoints and monitor for anomalous traffic patterns from unauthenticated sources.

Exploitation Status

Public Exploit Available: No confirmed public exploit (exploit_available: false).

Analyst Notes: As of August 1, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The vulnerability is highly exploitable due to the absence of authentication requirements for the affected functions.

Analyst Recommendation

Immediate remediation is required to secure the WordPress site against unauthorized manipulation. Administrators should update to version 3.1.1 immediately to close the authentication gap and prevent potential abuse of the plugin's functionality.

---METADATA---
VENDOR: WordPress
PRODUCT: Checkimate — WooCommerce Checkout, Abandoned Cart Recovery & Order Bumps
AFFECTED_VERSIONS: 0 through 1.0.13
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
The Checkimate WooCommerce plugin for WordPress is vulnerable to improper access control, allowing unauthenticated attackers to potentially perform unauthorized actions.

Executive Summary:
A critical access control vulnerability in the Checkimate WooCommerce plugin allows unauthenticated attackers to perform unauthorized actions, threatening e-commerce data integrity.

Vulnerability Details

CVE-ID: CVE-2026-14829

Affected Software: Checkimate — WooCommerce Checkout, Abandoned Cart Recovery & Order Bumps

Affected Versions: 0 through 1.0.13

Vulnerability: This is a CWE-284: Improper Access Control vulnerability. The flaw allows unauthenticated remote attackers to bypass security restrictions and perform unauthorized operations within the plugin context.

Business Impact

This vulnerability poses a major risk to e-commerce operations, as unauthorized access could lead to the modification of checkout processes, order manipulation, or data exposure. With a CVSS score of 8.2, the potential for financial loss and damage to customer trust is substantial.

Remediation Plan

Immediate Action: As no specific patch version is provided, users should immediately deactivate and remove the Checkimate plugin until a secure update is released by the vendor.

Proactive Monitoring: Audit recent order logs and user activity for suspicious entries or unauthorized changes to checkout configurations that may have occurred recently.

Compensating Controls: Deploy a Web Application Firewall with rules specifically designed to detect and block unauthorized access attempts targeting WordPress plugin endpoints.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of August 6, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The vulnerability is highly automatable, which increases the likelihood of opportunistic attacks.

Analyst Recommendation

Due to the lack of a confirmed patch and the existence of a proof-of-concept, the most secure course of action is to immediately remove the Checkimate plugin from your WordPress installation. Monitor vendor channels closely for the release of a security update before considering re-installation.

---METADATA---
VENDOR: Unknown
PRODUCT: Premium SEO
AFFECTED_VERSIONS: 0 and later
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
The Premium SEO WordPress plugin contains a malicious backdoor that enables unauthenticated attackers to create admin accounts, execute code, and inject arbitrary content into the site.

Executive Summary:
The Premium SEO WordPress plugin contains a malicious backdoor that grants unauthenticated attackers full control over the affected website.

Vulnerability Details

CVE-ID: CVE-2026-14812

Affected Software: Unknown Premium SEO

Affected Versions: 0 and later

Vulnerability: This vulnerability is classified as hidden functionality (CWE-912) due to the presence of an intentional, malicious backdoor. It allows an unauthenticated attacker to gain administrative access and execute arbitrary code on the server.

Business Impact

This represents a total compromise of the affected WordPress site. An attacker with full control can steal sensitive database information, distribute malware to site visitors, or use the server as a node for further attacks, resulting in severe reputational damage and potential loss of data.

Remediation Plan

Immediate Action: Immediately deactivate and remove the Premium SEO plugin from all WordPress installations. There is no safe version, as the software is inherently malicious.

Proactive Monitoring: Scan the WordPress database for unauthorized administrator accounts and check web server logs for suspicious remote code execution patterns.

Compensating Controls: Utilize a Web Application Firewall (WAF) to block malicious requests, though removal of the plugin remains the only effective mitigation.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of Aug 6, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. Because this is a malicious plugin, it should be considered compromised by design and removed entirely.

Analyst Recommendation

This is an extremely severe incident involving a malicious plugin. Organizations must perform an immediate audit of their WordPress installations to identify and purge this plugin. Any site where this plugin was installed should be considered fully compromised and subject to a thorough forensic review and password rotation for all administrative accounts.

---METADATA---
VENDOR: PROG MIS
PRODUCT: Prog Management System
AFFECTED_VERSIONS: PROG MIS Prog Management System: all
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
The PROG Management System contains a SQL injection vulnerability that allows unauthenticated remote attackers to execute arbitrary SQL commands and access database contents.

Executive Summary:
A critical SQL injection vulnerability in the PROG Management System enables unauthenticated attackers to exfiltrate sensitive data from the underlying database.

Vulnerability Details

CVE-ID: CVE-2026-14809

Affected Software: PROG MIS Prog Management System

Affected Versions: PROG MIS Prog Management System: all

Vulnerability: This is a classic CWE-89 SQL injection vulnerability. It allows an unauthenticated remote attacker to inject malicious SQL queries into the application, bypassing authentication and data access controls to retrieve unauthorized information.

Business Impact

With a CVSS score of 7.5 (High), this vulnerability poses a severe risk to data confidentiality. Successful exploitation could lead to full database compromise, resulting in the unauthorized disclosure of sensitive business or user information, potentially leading to regulatory non-compliance and significant reputational damage.

Remediation Plan

Immediate Action: Contact the vendor (PROG MIS) immediately to obtain the necessary security patch or remediation guidance as specified at https://www.twcert.org.tw/tw/cp-132-11025-fa1d9-1.html.

Proactive Monitoring: Review database access logs for anomalous query patterns, such as unexpected use of SQL keywords or high volumes of data retrieval requests.

Compensating Controls: Deploy a Web Application Firewall (WAF) with strict SQL injection protection rules to filter malicious traffic directed at the application.

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of July 6, 2026, there is no public information indicating active exploitation of this vulnerability. However, the lack of authentication required to exploit this flaw makes it a high-priority target for threat actors.

Analyst Recommendation

This vulnerability is critical due to the ease of access for unauthenticated attackers. Organizations using this system must take immediate steps to isolate the application from public access until a vendor-supplied patch is successfully applied and verified.

---METADATA---
VENDOR: PROG MIS
PRODUCT: Prog Management System
AFFECTED_VERSIONS: All
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
The PROG MIS Prog Management System contains an information exposure vulnerability that allows unauthenticated remote attackers to view sensitive database credentials via a specific application page.

Executive Summary:
A critical information exposure vulnerability in the PROG MIS Prog Management System enables unauthenticated remote attackers to obtain sensitive database account information.

Vulnerability Details

CVE-ID: CVE-2026-14808

Affected Software: PROG MIS Prog Management System

Affected Versions: All

Vulnerability: This vulnerability involves the Exposure of Sensitive Information to an unauthorized control sphere (CWE-497). An unauthenticated attacker can access a specific, unprotected page within the application to retrieve hard-coded database account names and passwords.

Business Impact

The exposure of database credentials allows an attacker to gain direct, unauthorized access to the backend data store. With a CVSS score of 9.8, this vulnerability presents a critical threat, enabling the exfiltration of sensitive business data, modification of records, or total administrative takeover of the database infrastructure.

Remediation Plan

Immediate Action: Contact the vendor immediately to secure the affected page and remove the exposure of sensitive configuration details.

Proactive Monitoring: Monitor database audit logs for unauthorized logins or unusual query patterns that deviate from standard application behavior.

Compensating Controls: Deploy a WAF to restrict public access to the specific application page identified as the entry point for this information leakage.

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of Jul 6, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

This vulnerability provides an easy path for attackers to gain credentials necessary for deeper network intrusion. Administrators should treat this as a high-priority incident and coordinate with the vendor to ensure the vulnerability is mitigated immediately.

---METADATA---
VENDOR: PROG MIS
PRODUCT: ERP App
AFFECTED_VERSIONS: All
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
The PROG MIS ERP App contains a hard-coded credentials vulnerability, allowing unauthenticated remote attackers to access application code and compromise database accounts.

Executive Summary:
A critical hard-coded credential vulnerability in the PROG MIS ERP App allows unauthenticated remote attackers to gain full access to sensitive database information and application code.

Vulnerability Details

CVE-ID: CVE-2026-14807

Affected Software: PROG MIS ERP App

Affected Versions: All

Vulnerability: This vulnerability is categorized as a Use of Hard-coded Credentials (CWE-798). It permits an unauthenticated remote attacker to bypass authentication mechanisms entirely, facilitating unauthorized access to the application’s underlying code and database credentials.

Business Impact

Successful exploitation of this vulnerability results in complete loss of confidentiality and integrity regarding the application and its connected database. Given the CVSS score of 9.8, this represents a critical risk that could lead to full system compromise, unauthorized data exfiltration of business-sensitive information, and long-term reputational damage.

Remediation Plan

Immediate Action: Contact the vendor immediately to obtain and apply the necessary security patches or configuration updates to remove hard-coded credentials.

Proactive Monitoring: Review database and application access logs for any anomalous connection attempts or unauthorized queries originating from unknown IP addresses.

Compensating Controls: Implement a Web Application Firewall (WAF) to filter malicious traffic and restrict access to sensitive endpoints until the application can be formally patched.

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of Jul 6, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

The presence of hard-coded credentials constitutes a severe security failure. Organizations using the PROG MIS ERP App must prioritize this issue and engage the vendor immediately for remediation. Failure to address this vulnerability poses an unacceptable risk of total system compromise.

---METADATA---
VENDOR: Bilin Software and Informatics Consultancy
PRODUCT: HUMANIST Digital Human Resources
AFFECTED_VERSIONS: 26.0 up to (excluding) 26.1
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
Bilin Software and Informatics Consultancy HUMANIST Digital Human Resources versions 26.0 before 26.1 contain a hard-coded cryptographic key, allowing for unauthorized access to sensitive constants.

Executive Summary:
A critical vulnerability involving hard-coded cryptographic keys in HUMANIST Digital Human Resources allows unauthenticated attackers to potentially read sensitive system constants.

Vulnerability Details

CVE-ID: CVE-2026-14804

Affected Software: Bilin Software and Informatics Consultancy HUMANIST Digital Human Resources

Affected Versions: 26.0 up to (excluding) 26.1

Vulnerability: This vulnerability is caused by the use of hard-coded cryptographic keys within the application, which facilitates unauthorized access. The CVSS vector confirms that this flaw is remotely exploitable by an unauthenticated attacker with low complexity.

Business Impact

The presence of hard-coded keys poses a severe risk to data confidentiality and integrity. With a CVSS score of 9.1, this vulnerability could allow attackers to bypass security controls, leading to the exposure of sensitive organizational data or the manipulation of system constants, potentially resulting in full system compromise.

Remediation Plan

Immediate Action: Upgrade to version 26.1 or the latest available version provided by Bilin Software and Informatics Consultancy to remove the hard-coded keys.

Proactive Monitoring: Review application access logs for unusual patterns or unauthorized attempts to retrieve configuration data or sensitive constants.

Compensating Controls: Ensure the application is isolated within a secure network segment and utilize a Web Application Firewall to block suspicious traffic patterns directed at the application's sensitive endpoints.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of August 4, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw's inherent exploitability is high due to the lack of required authentication.

Analyst Recommendation

Given the critical CVSS severity of 9.1, organizations running the affected versions of HUMANIST Digital Human Resources must prioritize this update. Immediate patching is the only effective way to eliminate the risk posed by the hard-coded cryptographic credentials.