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-2024-6143

Publication date:
19/06/2024
Actiontec WCB6200Q uh_tcp_recv_header Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Actiontec WCB6200Q routers. Authentication is not required to exploit this vulnerability.<br /> <br /> The specific flaw exists within the HTTP server. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length buffer. An attacker can leverage this vulnerability to execute code in the context of the HTTP server. Was ZDI-CAN-21414.
Severity CVSS v4.0: Pending analysis
Last modification:
19/09/2024

CVE-2024-5970

Publication date:
18/06/2024
The MaxGalleria plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin&amp;#39;s maxgallery_thumb shortcode in all versions up to, and including, 6.4.4 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Severity CVSS v4.0: Pending analysis
Last modification:
20/06/2024

CVE-2024-6129

Publication date:
18/06/2024
A vulnerability, which was classified as problematic, was found in spa-cartcms 1.9.0.6. Affected is an unknown function of the file /login of the component Username Handler. The manipulation of the argument email leads to observable behavioral discrepancy. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-268896.
Severity CVSS v4.0: Pending analysis
Last modification:
20/09/2024

CVE-2024-6128

Publication date:
18/06/2024
A vulnerability, which was classified as problematic, has been found in spa-cartcms 1.9.0.6. This issue affects some unknown processing of the file /checkout of the component Checkout Page. The manipulation of the argument quantity with the input -10 leads to enforcement of behavioral workflow. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-268895.
Severity CVSS v4.0: Pending analysis
Last modification:
20/09/2024

CVE-2024-38276

Publication date:
18/06/2024
Incorrect CSRF token checks resulted in multiple CSRF risks.
Severity CVSS v4.0: Pending analysis
Last modification:
26/03/2025

CVE-2024-38277

Publication date:
18/06/2024
A unique key should be generated for a user&amp;#39;s QR login key and their auto-login key, so the same key cannot be used interchangeably between the two.
Severity CVSS v4.0: Pending analysis
Last modification:
07/08/2025

CVE-2024-36974

Publication date:
18/06/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net/sched: taprio: always validate TCA_TAPRIO_ATTR_PRIOMAP<br /> <br /> If one TCA_TAPRIO_ATTR_PRIOMAP attribute has been provided,<br /> taprio_parse_mqprio_opt() must validate it, or userspace<br /> can inject arbitrary data to the kernel, the second time<br /> taprio_change() is called.<br /> <br /> First call (with valid attributes) sets dev-&gt;num_tc<br /> to a non zero value.<br /> <br /> Second call (with arbitrary mqprio attributes)<br /> returns early from taprio_parse_mqprio_opt()<br /> and bad things can happen.
Severity CVSS v4.0: Pending analysis
Last modification:
01/10/2025

CVE-2024-36975

Publication date:
18/06/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> KEYS: trusted: Do not use WARN when encode fails<br /> <br /> When asn1_encode_sequence() fails, WARN is not the correct solution.<br /> <br /> 1. asn1_encode_sequence() is not an internal function (located<br /> in lib/asn1_encode.c).<br /> 2. Location is known, which makes the stack trace useless.<br /> 3. Results a crash if panic_on_warn is set.<br /> <br /> It is also noteworthy that the use of WARN is undocumented, and it<br /> should be avoided unless there is a carefully considered rationale to<br /> use it.<br /> <br /> Replace WARN with pr_err, and print the return value instead, which is<br /> only useful piece of information.
Severity CVSS v4.0: Pending analysis
Last modification:
01/10/2025

CVE-2024-36976

Publication date:
18/06/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> Revert "media: v4l2-ctrls: show all owned controls in log_status"<br /> <br /> This reverts commit 9801b5b28c6929139d6fceeee8d739cc67bb2739.<br /> <br /> This patch introduced a potential deadlock scenario:<br /> <br /> [Wed May 8 10:02:06 2024] Possible unsafe locking scenario:<br /> <br /> [Wed May 8 10:02:06 2024] CPU0 CPU1<br /> [Wed May 8 10:02:06 2024] ---- ----<br /> [Wed May 8 10:02:06 2024] lock(vivid_ctrls:1620:(hdl_vid_cap)-&gt;_lock);<br /> [Wed May 8 10:02:06 2024] lock(vivid_ctrls:1608:(hdl_user_vid)-&gt;_lock);<br /> [Wed May 8 10:02:06 2024] lock(vivid_ctrls:1620:(hdl_vid_cap)-&gt;_lock);<br /> [Wed May 8 10:02:06 2024] lock(vivid_ctrls:1608:(hdl_user_vid)-&gt;_lock);<br /> <br /> For now just revert.
Severity CVSS v4.0: Pending analysis
Last modification:
29/08/2024

CVE-2024-36977

Publication date:
18/06/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> usb: dwc3: Wait unconditionally after issuing EndXfer command<br /> <br /> Currently all controller IP/revisions except DWC3_usb3 &gt;= 310a<br /> wait 1ms unconditionally for ENDXFER completion when IOC is not<br /> set. This is because DWC_usb3 controller revisions &gt;= 3.10a<br /> supports GUCTL2[14: Rst_actbitlater] bit which allows polling<br /> CMDACT bit to know whether ENDXFER command is completed.<br /> <br /> Consider a case where an IN request was queued, and parallelly<br /> soft_disconnect was called (due to ffs_epfile_release). This<br /> eventually calls stop_active_transfer with IOC cleared, hence<br /> send_gadget_ep_cmd() skips waiting for CMDACT cleared during<br /> EndXfer. For DWC3 controllers with revisions &gt;= 310a, we don&amp;#39;t<br /> forcefully wait for 1ms either, and we proceed by unmapping the<br /> requests. If ENDXFER didn&amp;#39;t complete by this time, it leads to<br /> SMMU faults since the controller would still be accessing those<br /> requests.<br /> <br /> Fix this by ensuring ENDXFER completion by adding 1ms delay in<br /> __dwc3_stop_active_transfer() unconditionally.
Severity CVSS v4.0: Pending analysis
Last modification:
01/10/2025

CVE-2024-37821

Publication date:
18/06/2024
An arbitrary file upload vulnerability in the Upload Template function of Dolibarr ERP CRM up to v19.0.1 allows attackers to execute arbitrary code via uploading a crafted .SQL file.
Severity CVSS v4.0: Pending analysis
Last modification:
13/06/2025

CVE-2024-38273

Publication date:
18/06/2024
Insufficient capability checks meant it was possible for users to gain access to BigBlueButton join URLs they did not have permission to access.
Severity CVSS v4.0: Pending analysis
Last modification:
07/08/2025