Vulnerabilities

With the aim of informing, warning and helping professionals with the latest security vulnerabilities in technology systems, we have made a database available for users interested in this information, which is in Spanish and includes all of the latest documented and recognised vulnerabilities.

This repository, with over 75,000 registers, is based on the information from the NVD (National Vulnerability Database) – by virtue of a partnership agreement – through which INCIBE translates the included information into Spanish.

On occasions this list will show vulnerabilities that have still not been translated, as they are added while the INCIBE team is still carrying out the translation process. The CVE  (Common Vulnerabilities and Exposures) Standard for Information Security Vulnerability Names is used with the aim to support the exchange of information between different tools and databases.

All vulnerabilities collected are linked to different information sources, as well as available patches or solutions provided by manufacturers and developers. It is possible to carry out advanced searches, as there is the option to select different criteria to narrow down the results, some examples being vulnerability types, manufacturers and impact levels, among others.

Through RSS feeds or Newsletters we can be informed daily about the latest vulnerabilities added to the repository. Below there is a list, updated daily, where you can discover the latest vulnerabilities.

CVE-2025-6023

Publication date:
18/07/2025
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
Severity CVSS v4.0: Pending analysis
Last modification:
22/07/2025

CVE-2025-6197

Publication date:
18/07/2025
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
Severity CVSS v4.0: Pending analysis
Last modification:
22/07/2025

CVE-2025-26854

Publication date:
18/07/2025
A SQL injection in Articles Good Search extension 1.0.0 - 1.2.4.0011 for Joomla allows attackers to execute arbitrary SQL commands.
Severity CVSS v4.0: Pending analysis
Last modification:
22/07/2025

CVE-2025-26855

Publication date:
18/07/2025
A SQL injection in Articles Calendar extension 1.0.0 - 1.0.1.0007 for Joomla allows attackers to execute arbitrary SQL commands.
Severity CVSS v4.0: Pending analysis
Last modification:
22/07/2025

CVE-2025-38349

Publication date:
18/07/2025
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).
Severity CVSS v4.0: Pending analysis
Last modification:
18/11/2025

CVE-2024-32124

Publication date:
18/07/2025
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.
Severity CVSS v4.0: Pending analysis
Last modification:
22/07/2025

CVE-2024-27779

Publication date:
18/07/2025
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.
Severity CVSS v4.0: Pending analysis
Last modification:
22/07/2025

CVE-2025-7772

Publication date:
18/07/2025
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.
Severity CVSS v4.0: Pending analysis
Last modification:
22/07/2025

CVE-2025-7438

Publication date:
18/07/2025
The MasterStudy LMS Pro plugin for WordPress is vulnerable to arbitrary file uploads due to insufficient file type validation in the &amp;#39;install_and_activate_plugin&amp;#39; function in all versions up to, and including, 4.7.9. This makes it possible for authenticated attackers, with Subscriber-level access and above, to upload arbitrary files on the affected site&amp;#39;s server which may make remote code execution possible. The vulnerability is difficult to exploit due to timing requirements and environmental factors.
Severity CVSS v4.0: Pending analysis
Last modification:
22/07/2025

CVE-2025-7643

Publication date:
18/07/2025
The Attachment Manager plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the handle_actions() function in all versions up to, and including, 2.1.2. This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).
Severity CVSS v4.0: Pending analysis
Last modification:
22/07/2025

CVE-2025-6717

Publication date:
18/07/2025
The B1.lt plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;id&amp;#39; parameter in all versions up to, and including, 2.2.56 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Severity CVSS v4.0: Pending analysis
Last modification:
22/07/2025

CVE-2025-6718

Publication date:
18/07/2025
The B1.lt plugin for WordPress is vulnerable to SQL Injection due to a missing capability check on the b1_run_query AJAX action in all versions up to, and including, 2.2.56. This makes it possible for authenticated attackers, with Subscriber-level access and above, to execute and run arbitrary SQL commands.
Severity CVSS v4.0: Pending analysis
Last modification:
22/07/2025