xamxte/cve-to-cwe huggingface dataset:
CVE-2024-38618: In the Linux kernel, the following vulnerability has been resolved:  ALSA: timer: Set lower bound of start tick time  Currently ALSA timer doesn't have the lower limit of the start tick time, and it allows a very small size, e.g. 1 tick with 1ns resolution for hrtimer.  Such a situation may lead to an unexpected RCU stall, where  the callback repeatedly queuing the expire update, as reported by fuzzer.  This patch introduces a sanity check of the timer start tick time, so that the system returns an error when a too small start size is set. As of this patch, the lower limit is hard-coded to 100us, which is small enough but can still work somehow.
CVE-2021-47582: In the Linux kernel, the following vulnerability has been resolved:  USB: core: Make do_proc_control() and do_proc_bulk() killable  The USBDEVFS_CONTROL and USBDEVFS_BULK ioctls invoke usb_start_wait_urb(), which contains an uninterruptible wait with a user-specified timeout value.  If timeout value is very large and the device being accessed does not respond in a reasonable amount of time, the kernel will complain about "Task X blocked for more than N seconds", as found in testing by syzbot:  INFO: task syz-executor.0:8700 blocked for more than 143 seconds.       Not tainted 5.14.0-rc7-syzkaller #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:syz-executor.0  state:D stack:23192 pid: 8700 ppid:  8455 flags:0x00004004 Call Trace:  context_switch kernel/sched/core.c:4681 [inline]  __schedule+0xc07/0x11f0 kernel/sched/core.c:5938  schedule+0x14b/0x210 kernel/sched/core.c:6017  schedule_timeout+0x98/0x2f0 kernel/time/timer.c:1857  do_wait_for_common+0x2da/0x480 kernel/sched/completion.c:85  __wait_for_common kernel/sched/completion.c:106 [inline]  wait_for_common kernel/sched/completion.c:117 [inline]  wait_for_completion_timeout+0x46/0x60 kernel/sched/completion.c:157  usb_start_wait_urb+0x167/0x550 drivers/usb/core/message.c:63  do_proc_bulk+0x978/0x1080 drivers/usb/core/devio.c:1236  proc_bulk drivers/usb/core/devio.c:1273 [inline]  usbdev_do_ioctl drivers/usb/core/devio.c:2547 [inline]  usbdev_ioctl+0x3441/0x6b10 drivers/usb/core/devio.c:2713 ...  To fix this problem, this patch replaces usbfs's calls to usb_control_msg() and usb_bulk_msg() with special-purpose code that does essentially the same thing (as recommended in the comment for usb_start_wait_urb()), except that it always uses a killable wait and it uses GFP_KERNEL rather than GFP_NOIO.
CVE-2021-47588: In the Linux kernel, the following vulnerability has been resolved:  sit: do not call ipip6_dev_free() from sit_init_net()  ipip6_dev_free is sit dev->priv_destructor, already called by register_netdevice() if something goes wrong.  Alternative would be to make ipip6_dev_free() robust against multiple invocations, but other drivers do not implement this strategy.  syzbot reported:  dst_release underflow WARNING: CPU: 0 PID: 5059 at net/core/dst.c:173 dst_release+0xd8/0xe0 net/core/dst.c:173 Modules linked in: CPU: 1 PID: 5059 Comm: syz-executor.4 Not tainted 5.16.0-rc5-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:dst_release+0xd8/0xe0 net/core/dst.c:173 Code: 4c 89 f2 89 d9 31 c0 5b 41 5e 5d e9 da d5 44 f9 e8 1d 90 5f f9 c6 05 87 48 c6 05 01 48 c7 c7 80 44 99 8b 31 c0 e8 e8 67 29 f9 <0f> 0b eb 85 0f 1f 40 00 53 48 89 fb e8 f7 8f 5f f9 48 83 c3 a8 48 RSP: 0018:ffffc9000aa5faa0 EFLAGS: 00010246 RAX: d6894a925dd15a00 RBX: 00000000ffffffff RCX: 0000000000040000 RDX: ffffc90005e19000 RSI: 000000000003ffff RDI: 0000000000040000 RBP: 0000000000000000 R08: ffffffff816a1f42 R09: ffffed1017344f2c R10: ffffed1017344f2c R11: 0000000000000000 R12: 0000607f462b1358 R13: 1ffffffff1bfd305 R14: ffffe8ffffcb1358 R15: dffffc0000000000 FS:  00007f66c71a2700(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f88aaed5058 CR3: 0000000023e0f000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  <TASK>  dst_cache_destroy+0x107/0x1e0 net/core/dst_cache.c:160  ipip6_dev_free net/ipv6/sit.c:1414 [inline]  sit_init_net+0x229/0x550 net/ipv6/sit.c:1936  ops_init+0x313/0x430 net/core/net_namespace.c:140  setup_net+0x35b/0x9d0 net/core/net_namespace.c:326  copy_net_ns+0x359/0x5c0 net/core/net_namespace.c:470  create_new_namespaces+0x4ce/0xa00 kernel/nsproxy.c:110  unshare_nsproxy_namespaces+0x11e/0x180 kernel/nsproxy.c:226  ksys_unshare+0x57d/0xb50 kernel/fork.c:3075  __do_sys_unshare kernel/fork.c:3146 [inline]  __se_sys_unshare kernel/fork.c:3144 [inline]  __x64_sys_unshare+0x34/0x40 kernel/fork.c:3144  do_syscall_x64 arch/x86/entry/common.c:50 [inline]  do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80  entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f66c882ce99 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f66c71a2168 EFLAGS: 00000246 ORIG_RAX: 0000000000000110 RAX: ffffffffffffffda RBX: 00007f66c893ff60 RCX: 00007f66c882ce99 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000048040200 RBP: 00007f66c8886ff1 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fff6634832f R14: 00007f66c71a2300 R15: 0000000000022000  </TASK>
CVE-2021-47607: In the Linux kernel, the following vulnerability has been resolved:  bpf: Fix kernel address leakage in atomic cmpxchg's r0 aux reg  The implementation of BPF_CMPXCHG on a high level has the following parameters:    .-[old-val]                                          .-[new-val]   BPF_R0 = cmpxchg{32,64}(DST_REG + insn->off, BPF_R0, SRC_REG)                           `-[mem-loc]          `-[old-val]  Given a BPF insn can only have two registers (dst, src), the R0 is fixed and used as an auxilliary register for input (old value) as well as output (returning old value from memory location). While the verifier performs a number of safety checks, it misses to reject unprivileged programs where R0 contains a pointer as old value.  Through brute-forcing it takes about ~16sec on my machine to leak a kernel pointer with BPF_CMPXCHG. The PoC is basically probing for kernel addresses by storing the guessed address into the map slot as a scalar, and using the map value pointer as R0 while SRC_REG has a canary value to detect a matching address.  Fix it by checking R0 for pointers, and reject if that's the case for unprivileged programs.
CVE-2021-47608: In the Linux kernel, the following vulnerability has been resolved:  bpf: Fix kernel address leakage in atomic fetch  The change in commit 37086bfdc737 ("bpf: Propagate stack bounds to registers in atomics w/ BPF_FETCH") around check_mem_access() handling is buggy since this would allow for unprivileged users to leak kernel pointers. For example, an atomic fetch/and with -1 on a stack destination which holds a spilled pointer will migrate the spilled register type into a scalar, which can then be exported out of the program (since scalar != pointer) by dumping it into a map value.  The original implementation of XADD was preventing this situation by using a double call to check_mem_access() one with BPF_READ and a subsequent one with BPF_WRITE, in both cases passing -1 as a placeholder value instead of register as per XADD semantics since it didn't contain a value fetch. The BPF_READ also included a check in check_stack_read_fixed_off() which rejects the program if the stack slot is of __is_pointer_value() if dst_regno < 0. The latter is to distinguish whether we're dealing with a regular stack spill/ fill or some arithmetical operation which is disallowed on non-scalars, see also 6e7e63cbb023 ("bpf: Forbid XADD on spilled pointers for unprivileged users") for more context on check_mem_access() and its handling of placeholder value -1.  One minimally intrusive option to fix the leak is for the BPF_FETCH case to initially check the BPF_READ case via check_mem_access() with -1 as register, followed by the actual load case with non-negative load_reg to propagate stack bounds to registers.
CVE-2021-47611: In the Linux kernel, the following vulnerability has been resolved:  mac80211: validate extended element ID is present  Before attempting to parse an extended element, verify that the extended element ID is present.
CVE-2021-47613: In the Linux kernel, the following vulnerability has been resolved:  i2c: virtio: fix completion handling  The driver currently assumes that the notify callback is only received when the device is done with all the queued buffers.  However, this is not true, since the notify callback could be called without any of the queued buffers being completed (for example, with virtio-pci and shared interrupts) or with only some of the buffers being completed (since the driver makes them available to the device in multiple separate virtqueue_add_sgs() calls).  This can lead to incorrect data on the I2C bus or memory corruption in the guest if the device operates on buffers which are have been freed by the driver.  (The WARN_ON in the driver is also triggered.)   BUG kmalloc-128 (Tainted: G        W        ): Poison overwritten  First byte 0x0 instead of 0x6b  Allocated in i2cdev_ioctl_rdwr+0x9d/0x1de age=243 cpu=0 pid=28   memdup_user+0x2e/0xbd   i2cdev_ioctl_rdwr+0x9d/0x1de   i2cdev_ioctl+0x247/0x2ed   vfs_ioctl+0x21/0x30   sys_ioctl+0xb18/0xb41  Freed in i2cdev_ioctl_rdwr+0x1bb/0x1de age=68 cpu=0 pid=28   kfree+0x1bd/0x1cc   i2cdev_ioctl_rdwr+0x1bb/0x1de   i2cdev_ioctl+0x247/0x2ed   vfs_ioctl+0x21/0x30   sys_ioctl+0xb18/0xb41  Fix this by calling virtio_get_buf() from the notify handler like other virtio drivers and by actually waiting for all the buffers to be completed.
CVE-2024-4565: The Advanced Custom Fields (ACF) WordPress plugin before 6.3, Advanced Custom Fields Pro WordPress plugin before 6.3 allows you to display custom field values for any post via shortcode without checking for the correct access
CVE-2022-48723: In the Linux kernel, the following vulnerability has been resolved:  spi: uniphier: fix reference count leak in uniphier_spi_probe()  The issue happens in several error paths in uniphier_spi_probe(). When either dma_get_slave_caps() or devm_spi_register_master() returns an error code, the function forgets to decrease the refcount of both `dma_rx` and `dma_tx` objects, which may lead to refcount leaks.  Fix it by decrementing the reference count of specific objects in those error paths.
CVE-2022-48725: In the Linux kernel, the following vulnerability has been resolved:  RDMA/siw: Fix refcounting leak in siw_create_qp()  The atomic_inc() needs to be paired with an atomic_dec() on the error path.
CVE-2022-48767: In the Linux kernel, the following vulnerability has been resolved:  ceph: properly put ceph_string reference after async create attempt  The reference acquired by try_prep_async_create is currently leaked. Ensure we put it.
CVE-2024-5156: The Flatsome theme for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's shortcode(s) in all versions up to, and including, 3.18.7 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.
CVE-2023-3352: The Smush plugin for WordPress is vulnerable to unauthorized deletion of the resmush list due to a missing capability check on the delete_resmush_list() function. This makes it possible for authenticated attackers, with minimal permissions such as a subscriber, to delete the resmush list for Nextgen or the Media Library.
CVE-2024-5503: The WP Blog Post Layouts plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.1.3. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary PHP files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.
CVE-2024-5455: The Plus Addons for Elementor Page Builder plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 5.5.4 via the 'magazine_style' parameter within the Dynamic Smart Showcase widget. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.
CVE-2024-36286: In the Linux kernel, the following vulnerability has been resolved:  netfilter: nfnetlink_queue: acquire rcu_read_lock() in instance_destroy_rcu()  syzbot reported that nf_reinject() could be called without rcu_read_lock() :  WARNING: suspicious RCU usage 6.9.0-rc7-syzkaller-02060-g5c1672705a1a #0 Not tainted  net/netfilter/nfnetlink_queue.c:263 suspicious rcu_dereference_check() usage!  other info that might help us debug this:  rcu_scheduler_active = 2, debug_locks = 1 2 locks held by syz-executor.4/13427:   #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:329 [inline]   #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_do_batch kernel/rcu/tree.c:2190 [inline]   #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_core+0xa86/0x1830 kernel/rcu/tree.c:2471   #1: ffff88801ca92958 (&inst->lock){+.-.}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:356 [inline]   #1: ffff88801ca92958 (&inst->lock){+.-.}-{2:2}, at: nfqnl_flush net/netfilter/nfnetlink_queue.c:405 [inline]   #1: ffff88801ca92958 (&inst->lock){+.-.}-{2:2}, at: instance_destroy_rcu+0x30/0x220 net/netfilter/nfnetlink_queue.c:172  stack backtrace: CPU: 0 PID: 13427 Comm: syz-executor.4 Not tainted 6.9.0-rc7-syzkaller-02060-g5c1672705a1a #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024 Call Trace:  <IRQ>   __dump_stack lib/dump_stack.c:88 [inline]   dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114   lockdep_rcu_suspicious+0x221/0x340 kernel/locking/lockdep.c:6712   nf_reinject net/netfilter/nfnetlink_queue.c:323 [inline]   nfqnl_reinject+0x6ec/0x1120 net/netfilter/nfnetlink_queue.c:397   nfqnl_flush net/netfilter/nfnetlink_queue.c:410 [inline]   instance_destroy_rcu+0x1ae/0x220 net/netfilter/nfnetlink_queue.c:172   rcu_do_batch kernel/rcu/tree.c:2196 [inline]   rcu_core+0xafd/0x1830 kernel/rcu/tree.c:2471   handle_softirqs+0x2d6/0x990 kernel/softirq.c:554   __do_softirq kernel/softirq.c:588 [inline]   invoke_softirq kernel/softirq.c:428 [inline]   __irq_exit_rcu+0xf4/0x1c0 kernel/softirq.c:637   irq_exit_rcu+0x9/0x30 kernel/softirq.c:649   instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1043 [inline]   sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1043  </IRQ>  <TASK>
CVE-2024-5596: The ARMember Premium plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 6.7. This is due to incorrectly implemented nonce validation function on multiple functions. This makes it possible for unauthenticated attackers to modify, or delete user meta and plugin options which can lead to limited privilege escalation.
CVE-2024-38663: In the Linux kernel, the following vulnerability has been resolved:  blk-cgroup: fix list corruption from resetting io stat  Since commit 3b8cc6298724 ("blk-cgroup: Optimize blkcg_rstat_flush()"), each iostat instance is added to blkcg percpu list, so blkcg_reset_stats() can't reset the stat instance by memset(), otherwise the llist may be corrupted.  Fix the issue by only resetting the counter part.
CVE-2024-6297: Several plugins for WordPress hosted on WordPress.org have been compromised and injected with malicious PHP scripts. A malicious threat actor compromised the source code of various plugins and injected code that exfiltrates database credentials and is used to create new, malicious, administrator users and send that data back to a server. Currently, not all plugins have been patched and we strongly recommend uninstalling the plugins for the time being and running a complete malware scan.
CVE-2024-5431: The WPCafe – Online Food Ordering, Restaurant Menu, Delivery, and Reservations for WooCommerce plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.2.25 via the reservation_extra_field shortcode parameter. This makes it possible for authenticated attackers, with Contributor-level access and above, to include remote files on the server, potentially resulting in code execution
CVE-2024-3249: The Zita Elementor Site Library plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the import_xml_data, xml_data_import, import_option_data, import_widgets, and import_customizer_settings functions in all versions up to, and including, 1.6.2. This makes it possible for authenticated attackers, with subscriber-level access and above, to create pages, update certain options, including WooCommerce page titles and Elementor settings, import widgets, and update the plugin's customizer settings and the WordPress custom CSS. NOTE: This vulnerability was partially fixed in version 1.6.2.
CVE-2024-6307: WordPress Core is vulnerable to Stored Cross-Site Scripting via the HTML API in various versions prior to 6.5.5 due to insufficient input sanitization and output escaping on URLs. 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.
CVE-2024-5451: The The7 — Website and eCommerce Builder for WordPress theme for WordPress is vulnerable to Stored Cross-Site Scripting via the 'url' attribute within the plugin's Icon and Heading widgets in all versions up to, and including, 11.13.0 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.
CVE-2024-39276: In the Linux kernel, the following vulnerability has been resolved:  ext4: fix mb_cache_entry's e_refcnt leak in ext4_xattr_block_cache_find()  Syzbot reports a warning as follows:  ============================================ WARNING: CPU: 0 PID: 5075 at fs/mbcache.c:419 mb_cache_destroy+0x224/0x290 Modules linked in: CPU: 0 PID: 5075 Comm: syz-executor199 Not tainted 6.9.0-rc6-gb947cc5bf6d7 RIP: 0010:mb_cache_destroy+0x224/0x290 fs/mbcache.c:419 Call Trace:  <TASK>  ext4_put_super+0x6d4/0xcd0 fs/ext4/super.c:1375  generic_shutdown_super+0x136/0x2d0 fs/super.c:641  kill_block_super+0x44/0x90 fs/super.c:1675  ext4_kill_sb+0x68/0xa0 fs/ext4/super.c:7327 [...] ============================================  This is because when finding an entry in ext4_xattr_block_cache_find(), if ext4_sb_bread() returns -ENOMEM, the ce's e_refcnt, which has already grown in the __entry_find(), won't be put away, and eventually trigger the above issue in mb_cache_destroy() due to reference count leakage.  So call mb_cache_entry_put() on the -ENOMEM error branch as a quick fix.
CVE-2024-39465: In the Linux kernel, the following vulnerability has been resolved:  media: mgb4: Fix double debugfs remove  Fixes an error where debugfs_remove_recursive() is called first on a parent directory and then again on a child which causes a kernel panic.  [hverkuil: added Fixes/Cc tags]
CVE-2024-34400: An issue was discovered in VirtoSoftware Virto Kanban Board Web Part before 5.3.5.1 for SharePoint 2019. There is /_layouts/15/Virto.KanbanTaskManager/api/KanbanData.ashx LinkTitle2 XSS.
CVE-2024-38526: pdoc provides API Documentation for Python Projects. Documentation generated with `pdoc --math` linked to JavaScript files from polyfill.io. The polyfill.io CDN has been sold and now serves malicious code. This issue has been fixed in pdoc 14.5.1.
CVE-2024-23765: An issue was discovered on HMS Anybus X-Gateway AB7832-F 3 devices. The gateway exposes an unidentified service on port 7412 on the network. All the network services of the gateway become unresponsive after sending 85 requests to this port. The content and length of the frame does not matter. The device needs to be restarted to resume operations.
CVE-2024-1330: The kadence-blocks-pro WordPress plugin before 2.3.8 does not prevent users with at least the contributor role using some of its shortcode's functionalities to leak arbitrary options from the database.
CVE-2024-6262: The Portfolio Gallery – Image Gallery Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'PFG' shortcode in all versions up to, and including, 1.6.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.
CVE-2024-5642: CPython 3.9 and earlier doesn't disallow configuring an empty list ("[]") for SSLContext.set_npn_protocols() which is an invalid value for the underlying OpenSSL API. This results in a buffer over-read when NPN is used (see CVE-2024-5535 for OpenSSL). This vulnerability is of low severity due to NPN being not widely used and specifying an empty list likely being uncommon in-practice (typically a protocol name would be configured).
CVE-2024-5863: The Easy Image Collage plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the ajax_image_collage() function in all versions up to, and including, 1.13.5. This makes it possible for authenticated attackers, with Contributor-level access and above, to erase all of the content in arbitrary posts.
CVE-2024-5864: The Easy Affiliate Links plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the eafl_reset_settings AJAX action in all versions up to, and including, 3.7.3. This makes it possible for authenticated attackers, with Subscriber-level access and above, to reset the plugin's settings.
CVE-2024-6296: The Stackable – Page Builder Gutenberg Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘data-caption’ parameter in all versions up to, and including, 3.13.1 due to insufficient input sanitization and output escaping. 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.
CVE-2024-2795: The SEO SIMPLE PACK plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 3.2.1 via META description. This makes it possible for unauthenticated attackers to extract limited information about password protected posts.
CVE-2024-5788: The Silesia theme for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘link’ attribute within the theme's Button shortcode in all versions up to, and including, 1.0.6 due to insufficient input sanitization and output escaping. 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.
CVE-2024-5796: The Infinite theme for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘project_url’ parameter in all versions up to, and including, 1.1.2 due to insufficient input sanitization and output escaping. 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.