Toret Manager Vulnerability (High) – CVE-2026-0912

Toret Manager Vulnerability (High) – CVE-2026-0912

by | Feb 18, 2026 | Plugins

Attack Vectors

Toret Manager (slug: toret-manager) versions up to and including 1.2.7 contain a High severity vulnerability (CVSS 8.8, CVE-2026-0912) that can be exploited by an authenticated user with Subscriber-level access or higher. This means an attacker does not need to “break in” from the outside first—any compromised low-privilege account (or an attacker who can create or obtain one) could be enough.

The issue occurs through WordPress AJAX actions tied to trman_save_option and trman_save_option_items, where a missing capability check can allow unauthorized changes to site settings. In practical terms, this can be used to update arbitrary WordPress options, including options that control registration behavior and default user roles.

Similar Attacks: WordPress option/privilege-escalation patterns have been used in real-world incidents, including large-scale plugin exploitation campaigns such as the ThemeGrill Demo Importer flaw leveraged to reset sites and create admin access, and mass exploitation of plugin vulnerabilities seen in campaigns like the WPForms vulnerability response coverage and the Essential Addons for Elementor exploit activity reporting.

Security Weakness

According to the published vulnerability details, the core weakness is a missing capability check in the affected functions. Capability checks are how WordPress ensures only appropriately privileged users (for example, Administrators) can change sensitive configuration.

Because this control is missing in affected versions of Toret Manager (≤ 1.2.7), a user who should only have limited access can potentially perform actions that impact the whole site—specifically, changing WordPress options in a way that can lead to privilege escalation.

There is no known patch available at the time of the advisory. That increases risk because the usual “update to a fixed version” response is not currently an option, and mitigation decisions become a business and operational tradeoff.

Technical or Business Impacts

This is a High risk issue because it can be used to gain administrative control of a WordPress site by changing options such as enabling user registration and setting the default registration role to Administrator, as described in the vulnerability summary. Once administrative access is obtained, attackers can typically change site content, redirect traffic, alter tracking pixels, create additional backdoor accounts, or install other plugins to persist.

For marketing directors and business owners, the immediate business impacts often include brand damage (defaced pages or malicious redirects), campaign disruption (paid traffic sent to compromised landing pages), and loss of trust if customers encounter warnings or suspicious behavior. SEO can also suffer if attackers inject spam content or manipulate site settings that affect indexing and reputation.

For executives and compliance teams, the downstream concerns include potential data exposure depending on what the attacker accesses after escalation, incident response costs, and governance issues if access controls are shown to be ineffective. Given the absence of a patch, many organizations will consider removing/uninstalling Toret Manager and replacing it, or applying compensating controls (such as restricting who can have accounts, tightening registration policies, and increased monitoring) based on risk tolerance and the site’s business criticality.

Vantage Vulnerability (Medium) – CVE-2026-5070

Attack Vectors CVE-2026-5070 is a Medium severity vulnerability (CVSS 6.4) affecting the Vantage WordPress theme (slug: vantage) in versions up to and including 1.20.32. It enables authenticated users with Contributor access or higher to inject malicious script into a...

WP Docs Vulnerability (Medium) – CVE-2026-3878

Attack Vectors CVE-2026-3878 is a Medium severity Stored Cross-Site Scripting (XSS) vulnerability (CVSS 6.4) affecting the WP Docs WordPress plugin (wp-docs) in versions 2.2.9 and below. The issue is exploitable by an authenticated user with Subscriber-level access or...

WPFore Subscribers