The WatchMan-Site7 WordPress plugin through 4.2.0 does not restrict access to its debugging console, which executes user-supplied PHP code, allowing any authenticated user, such as a subscriber, to run arbitrary code on the server.
Security readout for executives and security teams
Plain-English summary
WatchMan-Site7 exposes a debug console that lets even low-privileged WordPress users execute PHP on the server. Successful abuse could compromise website data, alter content, install persistent access, or disrupt service. The reported CVSS score is 9.9.
Executive priority
Treat as an immediate remediation priority on internet-facing or membership-enabled sites. Identify installations, disable the plugin where operationally feasible, and investigate potentially exposed systems. Prioritize sites holding sensitive data or allowing public account registration.
Technical view
CVE-2026-77009 is a CWE-94 code-injection flaw caused by missing access restrictions on the plugin’s debugging console. A network-accessible, authenticated subscriber can submit PHP for server-side execution without user interaction. The source description says versions through 4.2.0 are affected, although the structured affected entry lists only 3.1.1.
Likely exposure
WordPress sites using WatchMan-Site7 through 4.2.0 may be exposed, particularly where untrusted users can obtain subscriber accounts. The supplied affected-version data is inconsistent, so confirm installed versions and scope against current vendor or WPScan guidance.
Exploitation context
The WPScan reference is tagged as containing exploit and technical information, but the bundle provides no evidence of exploitation in the wild. The CVE is not listed as KEV in the supplied data. Exploitation requires an authenticated account, but subscriber-level access is sufficient.
Researcher notes
The CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. The core weakness is CWE-94. Evidence supports authenticated arbitrary PHP execution, but not active exploitation. Version scope needs confirmation because the narrative says through 4.2.0 while the structured affected list names 3.1.1 only.
Mitigation direction
Disable or remove WatchMan-Site7 until authoritative remediation guidance is available.
Check vendor and WPScan guidance for a fixed release or supported mitigation.
Restrict new user registration and remove unnecessary subscriber accounts.
Review affected sites for unauthorized changes and rotate credentials if compromise is suspected.
Validation and detection
Inventory WordPress sites for WatchMan-Site7 and record each installed version.
Confirm whether untrusted users can register or retain subscriber-level accounts.
Verify the debugging console is inaccessible to subscriber-level users.
Review server, WordPress, and security logs for suspicious authenticated activity or PHP execution.
Recheck authoritative guidance to resolve the affected-version inconsistency.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-94 · source CWE mapping
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.