High Severity Threats

The Mane WordPress theme by Elated-Themes contains a Local File Inclusion vulnerability in all versions up to and including 1.7. This vulnerability allows unauthenticated attackers to include and execute arbitrary files on the server, potentially leading to full code execution and access control bypass.

The FURUNO ELECTRIC FA-50 CLASS B AIS Transponder contains hard-coded credentials and lacks authentication for additional configuration. This vulnerability could allow unauthorized users to access and modify device settings without proper verification. No specific affected versions or patches are currently identified. There is no evidence of known exploits in the wild at this time.

CVE-2026-19892 is a high-severity privilege escalation vulnerability in the InfusedWoo Pro WordPress plugin. It affects all versions up to and including 5.1.17. The flaw arises from a missing proper authorization check in the ajax_iwar_preview_email() function, which relies solely on is_admin() for authorization. This allows authenticated users with subscriber-level access or higher to generate and retrieve password reset links for any WordPress user, including administrators, enabling account takeover.

Le-yan Medical Practice Management System version 2.4.2.8 contains a remote code execution vulnerability due to improper verification of the source of a communication channel. This flaw allows unauthenticated remote attackers to execute arbitrary operating system commands by delivering a crafted HTML page. The vulnerability is identified as CWE-940 and has a high severity with a CVSS score of 8.8.

GitPython versions prior to 3.1.59 contain a vulnerability in the TagReference.create() function that allows arbitrary file reads. This occurs because a positional reference parameter bypasses the unsafe option guard, enabling attackers to supply a crafted reference value such as --file=<path> to read arbitrary files. The contents of these files are then returned in the annotated tag message.

GitPython versions before 3.1.59 have an incomplete denylist in the unsafe_git_revision_options guard, which omits the --contents and -S options. This allows attackers to read arbitrary files by passing these options to the Repo.blame() method. By supplying revision values such as --contents=/etc/passwd, attackers can leak file contents through the blame result returned to the caller.

GitPython versions prior to 3.1.59 contain a path traversal vulnerability that allows attackers to create arbitrary git directories outside the intended clone destination. This occurs because the --separate-git-dir option is omitted from unsafe_git_clone_options, enabling attackers to redirect repository metadata to attacker-controlled filesystem paths via the separate_git_dir parameter in Repo.clone_from() or Repo.clone(). This can lead to arbitrary directory creation and potential execution of hooks.

GitPython versions before 3.1.59 contain a vulnerability where the merge_includes feature is not disabled when parsing .gitmodules files. This allows attackers to craft malicious .gitmodules files with include directives that reference arbitrary local file paths. When the repository's submodules are accessed, the GitConfigParser raises an exception that includes the first line of the targeted file, potentially disclosing sensitive local file content.

Grav versions prior to 2.0.16 have a vulnerability in the Twig sandbox configuration where the default denylist is incomplete. This allows attackers with page-edit permissions to access sensitive system configuration secrets via Twig template functions like config.get() or config.toArray() when config_access is enabled.

Grav CMS versions before 2.0.16 have a vulnerability where sandboxed Twig templates can access sensitive User object fields without proper filtering. This allows attackers with page-edit permissions to retrieve hashed passwords and two-factor authentication secrets. The vulnerability enables offline password cracking and potential authentication bypass.