Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
CVE ID: CVE-2022-49995 State: PUBLISHED Published: 2025-06-18T11:00:55.352Z Last Updated: 2025-06-18T11:00:55.352Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: writeback: avoid use-after-free after removing device When a disk is removed, bdi_unregister gets called to stop further writeback and wait for associated delayed work to complete. However, wb_inode_writeback_end() may schedule bandwidth estimation dwork after this has completed, which can result in the timer attempting to access the just freed bdi_writeback. Fix this by checking if the bdi_writeback is alive, similar to when scheduling writeback work. Since this requi
iteback. Fix this by checking if the bdi_writeback is alive, similar to when scheduling writeback work. Since this requires wb->work_lock, and wb_inode_writeback_end() may get called from interrupt, switch wb->work_lock to an irqsafe lock. References: - https://git.kernel.org/stable/c/f96b9f7c1676923bce871e728bb49c0dfa5013cc - https://git.kernel.org/stable/c/9a6c710f3bc10bc9cc23e1c080b53245b7f9d5b7 - https://git.kernel.org/stable/c/f87904c075515f3e1d8f4a7115869d3b914674fd
CVE ID: CVE-2022-49996 State: PUBLISHED Published: 2025-06-18T11:00:56.175Z Last Updated: 2025-06-18T11:00:56.175Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: btrfs: fix possible memory leak in btrfs_get_dev_args_from_path() In btrfs_get_dev_args_from_path(), btrfs_get_bdev_and_sb() can fail if the path is invalid. In this case, btrfs_get_dev_args_from_path() returns directly without freeing args->uuid and args->fsid allocated before, which causes memory leak. To fix these possible leaks, when btrfs_get_bdev_and_sb() fails, btrfs_put_dev_args_from_path() is called to clean up the memory. References: - https://git.kernel.org/
v_and_sb() fails, btrfs_put_dev_args_from_path() is called to clean up the memory. References: - https://git.kernel.org/stable/c/5f52402c77013e4a826394b807dd5ea4dc83bd72 - https://git.kernel.org/stable/c/4b124ad87244cd7f0883c5eaa38d2326b2154cad - https://git.kernel.org/stable/c/9ea0106a7a3d8116860712e3f17cd52ce99f6707
CVE ID: CVE-2022-49997 State: PUBLISHED Published: 2025-06-18T11:00:57.072Z Last Updated: 2025-06-18T11:00:57.072Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: lantiq_xrx200: restore buffer if memory allocation failed In a situation where memory allocation fails, an invalid buffer address is stored. When this descriptor is used again, the system panics in the build_skb() function when accessing memory. References: - https://git.kernel.org/stable/c/3ef2786e32d93e562cd40601248a14ae090de873 - https://git.kernel.org/stable/c/c9c3b1775f80fa21f5bff874027d2ccb10f5d90c
CVE ID: CVE-2022-49998 State: PUBLISHED Published: 2025-06-18T11:00:57.940Z Last Updated: 2025-06-18T11:00:57.940Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix locking in rxrpc's sendmsg Fix three bugs in the rxrpc's sendmsg implementation: (1) rxrpc_new_client_call() should release the socket lock when returning an error from rxrpc_get_call_slot(). (2) rxrpc_wait_for_tx_window_intr() will return without the call mutex held in the event that we're interrupted by a signal whilst waiting for tx space on the socket or relocking the call mutex afterwards. Fix this by: (a) moving the unlock/lock of the call mutex up to
e on the socket or relocking the call mutex afterwards. Fix this by: (a) moving the unlock/lock of the call mutex up to rxrpc_send_data() such that the lock is not held around all of rxrpc_wait_for_tx_window*() and (b) indicating to higher callers whether we're return with the lock dropped. Note that this means recvmsg() will not block on this call whilst we're waiting. (3) After dropping and regaining the call mutex, rxrpc_send_data() needs to go and recheck the state of the tx_pending buffer and the tx_total_len check in case we raced with another sendmsg() on the same call. Thinking on this some more, it might make sense to have different locks for sendmsg() and recvmsg(). There's probabl
ll. Thinking on this some more, it might make sense to have different locks for sendmsg() and recvmsg(). There's probably no need to make recvmsg() wait for sendmsg(). It does mean that recvmsg() can return MSG_EOR indicating that a call is dead before a sendmsg() to that call returns - but that can currently happen anyway. Without fix (2), something like the following can be induced: WARNING: bad unlock balance detected! 5.16.0-rc6-syzkaller #0 Not tainted ------------------------------------- syz-executor011/3597 is trying to release lock (&call->user_mutex) at: [<ffffffff885163a3>] rxrpc_do_sendmsg+0xc13/0x1350 net/rxrpc/sendmsg.c:748 but there are no more locks to release! other info tha
f885163a3>] rxrpc_do_sendmsg+0xc13/0x1350 net/rxrpc/sendmsg.c:748 but there are no more locks to release! other info that might help us debug this: no locks held by syz-executor011/3597. ... Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 print_unlock_imbalance_bug include/trace/events/lock.h:58 [inline] __lock_release kernel/locking/lockdep.c:5306 [inline] lock_release.cold+0x49/0x4e kernel/locking/lockdep.c:5657 __mutex_unlock_slowpath+0x99/0x5e0 kernel/locking/mutex.c:900 rxrpc_do_sendmsg+0xc13/0x1350 net/rxrpc/sendmsg.c:748 rxrpc_sendmsg+0x420/0x630 net/rxrpc/af_rxrpc.c:561 sock_sendmsg_nosec net/socket.c:704 [inline] sock_sendm
sendmsg.c:748 rxrpc_sendmsg+0x420/0x630 net/rxrpc/af_rxrpc.c:561 sock_sendmsg_nosec net/socket.c:704 [inline] sock_sendmsg+0xcf/0x120 net/socket.c:724 ____sys_sendmsg+0x6e8/0x810 net/socket.c:2409 ___sys_sendmsg+0xf3/0x170 net/socket.c:2463 __sys_sendmsg+0xe5/0x1b0 net/socket.c:2492 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae [Thanks to Hawkins Jiawei and Khalid Masum for their attempts to fix this] References: - https://git.kernel.org/stable/c/79e2ca7aa96e80961828ab6312264633b66183cc - https://git.kernel.org/stable/c/2bc769b8edb158be7379d15f36e23d66cf850053 - https://git.kernel.org/stable/c/09
b66183cc - https://git.kernel.org/stable/c/2bc769b8edb158be7379d15f36e23d66cf850053 - https://git.kernel.org/stable/c/091dc91e119fdd61432347231724f4e861c6b465 - https://git.kernel.org/stable/c/b0f571ecd7943423c25947439045f0d352ca3dbf
CVE ID: CVE-2022-49999 State: PUBLISHED Published: 2025-06-18T11:00:58.916Z Last Updated: 2025-06-18T11:00:58.916Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: btrfs: fix space cache corruption and potential double allocations When testing space_cache v2 on a large set of machines, we encountered a few symptoms: 1. "unable to add free space :-17" (EEXIST) errors. 2. Missing free space info items, sometimes caught with a "missing free space info for X" error. 3. Double-accounted space: ranges that were allocated in the extent tree and also marked as free in the free space tree, ranges that were marked as allocated twice in the
ted in the extent tree and also marked as free in the free space tree, ranges that were marked as allocated twice in the extent tree, or ranges that were marked as free twice in the free space tree. If the latter made it onto disk, the next reboot would hit the BUG_ON() in add_new_free_space(). 4. On some hosts with no on-disk corruption or error messages, the in-memory space cache (dumped with drgn) disagreed with the free space tree. All of these symptoms have the same underlying cause: a race between caching the free space for a block group and returning free space to the in-memory space cache for pinned extents causes us to double-add a free range to the space cache. This race exists whe
e in-memory space cache for pinned extents causes us to double-add a free range to the space cache. This race exists when free space is cached from the free space tree (space_cache=v2) or the extent tree (nospace_cache, or space_cache=v1 if the cache needs to be regenerated). struct btrfs_block_group::last_byte_to_unpin and struct btrfs_block_group::progress are supposed to protect against this race, but commit d0c2f4fa555e ("btrfs: make concurrent fsyncs wait less when waiting for a transaction commit") subtly broke this by allowing multiple transactions to be unpinning extents at the same time. Specifically, the race is as follows: 1. An extent is deleted from an uncached block group in tr
tents at the same time. Specifically, the race is as follows: 1. An extent is deleted from an uncached block group in transaction A. 2. btrfs_commit_transaction() is called for transaction A. 3. btrfs_run_delayed_refs() -> __btrfs_free_extent() runs the delayed ref for the deleted extent. 4. __btrfs_free_extent() -> do_free_extent_accounting() -> add_to_free_space_tree() adds the deleted extent back to the free space tree. 5. do_free_extent_accounting() -> btrfs_update_block_group() -> btrfs_cache_block_group() queues up the block group to get cached. block_group->progress is set to block_group->start. 6. btrfs_commit_transaction() for transaction A calls switch_commit_roots(). It sets block
is set to block_group->start. 6. btrfs_commit_transaction() for transaction A calls switch_commit_roots(). It sets block_group->last_byte_to_unpin to block_group->progress, which is block_group->start because the block group hasn't been cached yet. 7. The caching thread gets to our block group. Since the commit roots were already switched, load_free_space_tree() sees the deleted extent as free and adds it to the space cache. It finishes caching and sets block_group->progress to U64_MAX. 8. btrfs_commit_transaction() advances transaction A to TRANS_STATE_SUPER_COMMITTED. 9. fsync calls btrfs_commit_transaction() for transaction B. Since transaction A is already in TRANS_STATE_SUPER_COMMITTED
fsync calls btrfs_commit_transaction() for transaction B. Since transaction A is already in TRANS_STATE_SUPER_COMMITTED and the commit is for fsync, it advances. 10. btrfs_commit_transaction() for transaction B calls switch_commit_roots(). This time, the block group has already been cached, so it sets block_group->last_byte_to_unpin to U64_MAX. 11. btrfs_commit_transaction() for transaction A calls btrfs_finish_extent_commit(), which calls unpin_extent_range() for the deleted extent. It sees last_byte_to_unpin set to U64_MAX (by transaction B!), so it adds the deleted extent to the space cache again! This explains all of our symptoms above: * If the sequence of events is exactly as described
t to the space cache again! This explains all of our symptoms above: * If the sequence of events is exactly as described above, when the free space is re-added in step 11, it will fail with EEXIST. * If another thread reallocates the deleted extent in between steps 7 and 11, then step 11 will silently re-add that space to the space cache as free even though it is actually allocated. Then, if that space is allocated *again*, the free space tree will be corrupted (namely, the wrong item will be deleted). * If we don't catch this free space tree corr ---truncated--- References: - https://git.kernel.org/stable/c/92dc4c1a8e58bcc7a183a4c86b055c24cc88d967 - https://git.kernel.org/stable/c/a2e54eb64
: - https://git.kernel.org/stable/c/92dc4c1a8e58bcc7a183a4c86b055c24cc88d967 - https://git.kernel.org/stable/c/a2e54eb64229f07f917b05d0c323604fda9b89f7 - https://git.kernel.org/stable/c/ced8ecf026fd8084cf175530ff85c76d6085d715
CVE ID: CVE-2022-4000 State: PUBLISHED Published: 2022-12-12T17:54:56.948Z Last Updated: 2025-04-22T14:48:02.131Z Vendors: Unknown Products: WooCommerce Shipping Problem Types: CWE-79 Cross-Site Scripting (XSS) Description: The WooCommerce Shipping WordPress plugin through 1.2.11 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup). Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://wpscan.com/vulnerability/5563c030-bd62-4839-98e8-84bc8191e242
CVE ID: CVE-2022-4001 State: PUBLISHED Published: 2024-07-31T20:30:09.455Z Last Updated: 2024-08-01T13:37:34.910Z Severity: HIGH (CVSS 7.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L) Vendors: Motorola Products: Q14 Mesh Router Firmware Problem Types: CWE-287 Description: An authentication bypass vulnerability could allow an attacker to access API functions without authentication. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://en-us.support.motorola.com/app/answers/detail/a_id/176952/~/motorola-q14-mesh-router-vulnerabilities
CVE ID: CVE-2022-4002 State: PUBLISHED Published: 2024-07-31T20:29:59.495Z Last Updated: 2024-08-06T19:28:56.303Z Severity: HIGH (CVSS 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) Vendors: Motorola Products: Q14 Mesh Router Firmware Problem Types: CWE-287 Description: A command injection vulnerability could allow an authenticated user to execute operating system commands as root via a specially crafted API request. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://en-us.support.motorola.com/app/answers/detail/a_id/176952/~/motorola-q14-mesh-router-vulnerabilities
CVE ID: CVE-2022-4003 State: PUBLISHED Published: 2024-07-31T20:29:48.894Z Last Updated: 2024-07-31T21:02:13.515Z Severity: LOW (CVSS 2.7 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L) Vendors: Motorola Products: Q14 Mesh Router Firmware Problem Types: CWE-400 Description: A denial-of-service vulnerability could allow an authenticated user to trigger an internal service restart via a specially crafted API request. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://en-us.support.motorola.com/app/answers/detail/a_id/176952/~/motorola-q14-mesh-router-vulnerabilities
CVE ID: CVE-2022-4004 State: PUBLISHED Published: 2022-12-12T17:54:42.964Z Last Updated: 2025-04-22T14:59:56.162Z Vendors: Unknown Products: Donation Button Problem Types: CWE-862 Missing Authorization Description: The Donation Button WordPress plugin through 4.0.0 does not properly check for privileges and nonce tokens in its "donation_button_twilio_send_test_sms" AJAX action, which may allow any users with an account on the affected site, like subscribers, to use the plugin's Twilio integration to send SMSes to arbitrary phone numbers. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://wpscan.com/vulnerability/6a3bcfb3-3ede-459d-969f-b7b30dafd
ram Container: - CISA ADP Vulnrichment: References: - https://wpscan.com/vulnerability/6a3bcfb3-3ede-459d-969f-b7b30dafd098
CVE ID: CVE-2022-4005 State: PUBLISHED Published: 2022-12-12T17:54:39.478Z Last Updated: 2025-04-22T15:07:18.933Z Vendors: Unknown Products: Donation Button Problem Types: CWE-79 Cross-Site Scripting (XSS) Description: The Donation Button WordPress plugin through 4.0.0 does not sanitize and escapes some parameters, which could allow users with a role as low as Contributor to perform Cross-Site Scripting attacks. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://wpscan.com/vulnerability/61d5c9b8-5c21-4ab5-b31c-e13ca19ea25c
CVE ID: CVE-2022-4006 State: PUBLISHED Published: 2022-11-15T00:00:00.000Z Last Updated: 2025-04-15T13:13:26.903Z Severity: LOW (CVSS 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N) Vendors: WBCE Products: CMS Problem Types: CWE-400 Description: A vulnerability, which was classified as problematic, has been found in WBCE CMS. Affected by this issue is the function increase_attempts of the file wbce/framework/class.login.php of the component Header Handler. The manipulation of the argument X-Forwarded-For leads to improper restriction of excessive authentication attempts. The attack may be launched remotely. The name of the patch is d394ba39a7bfeb31eda797b6195fd90ef74b2e75. It is recommende
The attack may be launched remotely. The name of the patch is d394ba39a7bfeb31eda797b6195fd90ef74b2e75. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-213716. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/WBCE/WBCE_CMS/issues/524 - https://github.com/wbce/wbce_cms/commit/d394ba39a7bfeb31eda797b6195fd90ef74b2e75 - https://vuldb.com/?id.213716
CVE ID: CVE-2022-4007 State: PUBLISHED Published: 2023-03-08T00:00:00.000Z Last Updated: 2025-03-12T19:52:24.294Z Severity: MEDIUM (CVSS 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N) Vendors: GitLab Products: GitLab Problem Types: Improper neutralization of input during web page generation ('cross-site scripting') in GitLab Description: A issue has been discovered in GitLab CE/EE affecting all versions from 15.3 prior to 15.7.8, version 15.8 prior to 15.8.4, and version 15.9 prior to 15.9.2 A cross-site scripting vulnerability was found in the title field of work items that allowed attackers to perform arbitrary actions on behalf of victims at client side. Additional Analyst Notes: - CVE
that allowed attackers to perform arbitrary actions on behalf of victims at client side. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://gitlab.com/gitlab-org/gitlab/-/issues/382789 - https://hackerone.com/reports/1767745 - https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-4007.json
CVE ID: CVE-2022-4008 State: PUBLISHED Published: 2023-05-10T00:00:00.000Z Last Updated: 2025-01-28T15:04:16.647Z Vendors: Octopus Deploy Products: Octopus Tentacle Problem Types: Zipbomb resource exhaustion Description: In affected versions of Octopus Deploy it is possible to upload a zipbomb file as a task which results in Denial of Service Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://advisories.octopus.com/post/2023/sa2023-08/
CVE ID: CVE-2022-4009 State: PUBLISHED Published: 2023-03-16T00:00:00.000Z Last Updated: 2025-02-26T20:17:44.044Z Vendors: Octopus Deploy Products: Octopus Server Problem Types: Command injection via offline package creation Description: In affected versions of Octopus Deploy it is possible for a user to introduce code via offline package creation Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://advisories.octopus.com/post/2023/sa2023-05/
CVE ID: CVE-2022-4010 State: PUBLISHED Published: 2022-12-12T17:54:50.528Z Last Updated: 2025-04-22T17:52:23.221Z Vendors: Unknown Products: Image Hover Effects Problem Types: CWE-79 Cross-Site Scripting (XSS) Description: The Image Hover Effects WordPress plugin before 5.5 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup). Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://wpscan.com/vulnerability/bed8c81c-04c7-412d-9563-ce4eb64b7754
CVE ID: CVE-2022-4011 State: PUBLISHED Published: 2022-11-16T00:00:00.000Z Last Updated: 2025-04-14T15:55:48.979Z Severity: MEDIUM (CVSS 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L) Vendors: unspecified Products: Simple History Plugin Problem Types: CWE-707 Description: A vulnerability was found in Simple History Plugin. It has been rated as critical. This issue affects some unknown processing of the component Header Handler. The manipulation of the argument X-Forwarded-For leads to improper output neutralization for logs. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-213785 was assigned to this vulnerability. Addi
oit has been disclosed to the public and may be used. The identifier VDB-213785 was assigned to this vulnerability. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://drive.google.com/file/d/142cPciqIhNbfKhhxIwbrYFTegLvnwin_/view - https://drive.google.com/file/d/1AJXip8UG_ADbxtokPzAb61-lEg-xLebZ/view - https://vuldb.com/?id.213785
CVE ID: CVE-2022-4012 State: PUBLISHED Published: 2022-11-16T00:00:00.000Z Last Updated: 2025-04-15T13:13:18.149Z Severity: MEDIUM (CVSS 6.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L) Vendors: unspecified Products: Hospital Management Center Problem Types: CWE-707 Description: A vulnerability classified as critical has been found in Hospital Management Center. Affected is an unknown function of the file patient-info.php. The manipulation of the argument pt_id leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. VDB-213786 is the identifier assigned to this vulnerability. Additional Analyst Notes: - CVE Program
c and may be used. VDB-213786 is the identifier assigned to this vulnerability. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/golamsarwar08/hms/issues/1 - https://vuldb.com/?id.213786
CVE ID: CVE-2022-4013 State: PUBLISHED Published: 2022-11-16T00:00:00.000Z Last Updated: 2025-04-15T13:13:09.692Z Severity: MEDIUM (CVSS 4.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N) Vendors: unspecified Products: Hospital Management Center Problem Types: CWE-863 Description: A vulnerability classified as problematic was found in Hospital Management Center. Affected by this vulnerability is an unknown functionality of the file appointment.php. The manipulation leads to cross-site request forgery. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-213787. Additional Analyst Notes: - CVE
public and may be used. The associated identifier of this vulnerability is VDB-213787. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/golamsarwar08/hms/issues/2 - https://vuldb.com/?id.213787
CVE ID: CVE-2022-4014 State: PUBLISHED Published: 2022-11-16T00:00:00 Last Updated: 2024-08-03T01:27:54.169Z Severity: MEDIUM (CVSS 4.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N) Vendors: unspecified Products: FeehiCMS Problem Types: CWE-863 Description: A vulnerability, which was classified as problematic, has been found in FeehiCMS. Affected by this issue is some unknown functionality of the component Post My Comment Tab. The manipulation leads to cross-site request forgery. The attack may be launched remotely. The identifier of this vulnerability is VDB-213788. Additional Analyst Notes: - CVE Program Container: References: - https://vuldb.com/?id.213788
CVE ID: CVE-2022-4015 State: PUBLISHED Published: 2022-11-16T00:00:00 Last Updated: 2024-08-03T01:27:54.058Z Severity: MEDIUM (CVSS 4.7 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L) Vendors: unspecified Products: Sports Club Management System Problem Types: CWE-707 Description: A vulnerability, which was classified as critical, was found in Sports Club Management System 119. This affects an unknown part of the file admin/make_payments.php. The manipulation of the argument m_id/plan leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-213789 was assigned to this vulnerability. Additional Analys
disclosed to the public and may be used. The identifier VDB-213789 was assigned to this vulnerability. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/shreyansh225/Sports-Club-Management-System/issues/6 - https://vuldb.com/?id.213789