Vulnerabilities

A stored XSS vulnerability in the Balbooa Gallery plugin 1.0.0-2.4.0 for Joomla allows privileged users to store malicious scripts in gallery items.

Time-of-check to time-of-use race condition vulnerability potentially allowed an attacker to use the installed ESET security software to clear the content of an arbitrary file on the file system.

The LoginPress Pro plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 5.0.1. This is due to insufficient verification on the user being returned by the social login token. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if they have access to the email and the user does not have an already-existing account for the service returning the token.

Mattermost versions 10.5.x

An open redirect vulnerability has been identified in Grafana OSS that can be exploited to achieve XSS attacks. The vulnerability was introduced in Grafana v11.5.0.<br /> <br /> The open redirect can be chained with path traversal vulnerabilities to achieve XSS.<br /> <br /> Fixed in versions 12.0.2+security-01, 11.6.3+security-01, 11.5.6+security-01, 11.4.6+security-01 and 11.3.8+security-01

An open redirect vulnerability has been identified in Grafana OSS organization switching functionality.<br /> <br /> <br /> Prerequisites for exploitation:<br /> <br /> - Multiple organizations must exist in the Grafana instance<br /> <br /> - Victim must be on a different organization than the one specified in the URL

A SQL injection in Articles Good Search extension 1.0.0 - 1.2.4.0011 for Joomla allows attackers to execute arbitrary SQL commands.

A SQL injection in Articles Calendar extension 1.0.0 - 1.0.1.0007 for Joomla allows attackers to execute arbitrary SQL commands.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> eventpoll: don&amp;#39;t decrement ep refcount while still holding the ep mutex<br /> <br /> Jann Horn points out that epoll is decrementing the ep refcount and then<br /> doing a<br /> <br /> mutex_unlock(&amp;ep-&gt;mtx);<br /> <br /> afterwards. That&amp;#39;s very wrong, because it can lead to a use-after-free.<br /> <br /> That pattern is actually fine for the very last reference, because the<br /> code in question will delay the actual call to "ep_free(ep)" until after<br /> it has unlocked the mutex.<br /> <br /> But it&amp;#39;s wrong for the much subtler "next to last" case when somebody<br /> *else* may also be dropping their reference and free the ep while we&amp;#39;re<br /> still using the mutex.<br /> <br /> Note that this is true even if that other user is also using the same ep<br /> mutex: mutexes, unlike spinlocks, can not be used for object ownership,<br /> even if they guarantee mutual exclusion.<br /> <br /> A mutex "unlock" operation is not atomic, and as one user is still<br /> accessing the mutex as part of unlocking it, another user can come in<br /> and get the now released mutex and free the data structure while the<br /> first user is still cleaning up.<br /> <br /> See our mutex documentation in Documentation/locking/mutex-design.rst,<br /> in particular the section [1] about semantics:<br /> <br /> "mutex_unlock() may access the mutex structure even after it has<br /> internally released the lock already - so it&amp;#39;s not safe for<br /> another context to acquire the mutex and assume that the<br /> mutex_unlock() context is not using the structure anymore"<br /> <br /> So if we drop our ep ref before the mutex unlock, but we weren&amp;#39;t the<br /> last one, we may then unlock the mutex, another user comes in, drops<br /> _their_ reference and releases the &amp;#39;ep&amp;#39; as it now has no users - all<br /> while the mutex_unlock() is still accessing it.<br /> <br /> Fix this by simply moving the ep refcount dropping to outside the mutex:<br /> the refcount itself is atomic, and doesn&amp;#39;t need mutex protection (that&amp;#39;s<br /> the whole _point_ of refcounts: unlike mutexes, they are inherently<br /> about object lifetimes).

An improper access control vulnerability [CWE-284] in FortiIsolator version 2.4.4, version 2.4.3, 2.3 all versions logging component may allow a remote authenticated read-only attacker to alter logs via a crafted HTTP request.

An insufficient session expiration vulnerability [CWE-613] in FortiSandbox FortiSandbox version 4.4.4 and below, version 4.2.6 and below, 4.0 all versions, 3.2 all versions and FortiIsolator version 2.4 and below, 2.3 all versions, 2.2 all versions, 2.1 all versions, 2.0 all versions, 1.2 all versions may allow a remote attacker in possession of an admin session cookie to keep using that admin&amp;#39;s session even after the admin user was deleted.

The Malcure Malware Scanner — #1 Toolset for WordPress Malware Removal plugin for WordPress is vulnerable to Arbitrary File Read in all versions up to, and including, 16.8 via the wpmr_inspect_file() function due to a missing capability check. This makes it possible for authenticated attackers, with subscriber-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information.