deardaniel/secdata-raw huggingface dataset:
CVE: CVE-2025-39822
Published: 2025-09-16
Description: In the Linux kernel, the following vulnerability has been resolved:

io_uring/kbuf: fix signedness in this_len calculation

When importing and using buffers, buf->len is considered unsigned.
However, buf->len is converted to signed int when committing. This can
lead to unexpected behavior if the buffer is large enough to be
interpreted as a negative value. Make min_t calculation unsigned.
CVSS Score: 5.5 (MEDIUM)
References: https://git.kernel.org/stable/c/c64eff368ac676e8540344d27a3de47e0ad90d21; https://git.kernel.org/stable/c/f4f411c068402c370c4f9a9d4950a97af97bbbb1
CVE: CVE-2025-39823
Published: 2025-09-16
Description: In the Linux kernel, the following vulnerability has been resolved:

KVM: x86: use array_index_nospec with indices that come from guest

min and dest_id are guest-controlled indices. Using array_index_nospec()
after the bounds checks clamps these values to mitigate speculative execution
side-channels.
CVSS Score: 7.8 (HIGH)
CWE: CWE-129
References: https://git.kernel.org/stable/c/31a0ad2f60cb4816e06218b63e695eb72ce74974; https://git.kernel.org/stable/c/33e974c2d5a82b2f9d9ba0ad9cbaabc1c8e3985f; https://git.kernel.org/stable/c/67a05679621b7f721bdba37a5d18665d3aceb695
CVE: CVE-2025-39825
Published: 2025-09-16
Description: In the Linux kernel, the following vulnerability has been resolved:

smb: client: fix race with concurrent opens in rename(2)

Besides sending the rename request to the server, the rename process
also involves closing any deferred close, waiting for outstanding I/O
to complete as well as marking all existing open handles as deleted to
prevent them from deferring closes, which increases the race window
for potential concurrent opens on the target file.

Fix this by unhashing the dentry in advance to prevent any concurrent
opens on the target.
CVSS Score: 4.7 (MEDIUM)
CWE: CWE-362
References: https://git.kernel.org/stable/c/24b9ed739c8c5b464d983e12cf308982f3ae93c2; https://git.kernel.org/stable/c/289f945acb20b9b54fe4d13895e44aa58965ddb2; https://git.kernel.org/stable/c/c9991af5e09924f6f3b3e6996a5e09f9504b4358
CVE: CVE-2025-39826
Published: 2025-09-16
Description: In the Linux kernel, the following vulnerability has been resolved:

net: rose: convert 'use' field to refcount_t

The 'use' field in struct rose_neigh is used as a reference counter but
lacks atomicity. This can lead to race conditions where a rose_neigh
structure is freed while still being referenced by other code paths.

For example, when rose_neigh->use becomes zero during an ioctl operation
via rose_rt_ioctl(), the structure may be removed while its timer is
still active, potentially causing use-after-free issues.

This patch changes the type of 'use' from unsigned short to refcount_t and
updates all code paths to use rose_neigh_hold() and rose_neigh_put() which
operate reference counts atomically.
CVSS Score: 7.0 (HIGH)
CWE: CWE-416
References: https://git.kernel.org/stable/c/0085b250fcc79f900c82a69980ec2f3e1871823b; https://git.kernel.org/stable/c/203e4f42596ede[PII_REDACTED]8716a3db6dbb7f51; https://git.kernel.org/stable/c/d860d1faa6b2ce3becfdb8b0c2b048ad31800061
CVE: CVE-2025-39827
Published: 2025-09-16
Description: In the Linux kernel, the following vulnerability has been resolved:

net: rose: include node references in rose_neigh refcount

Current implementation maintains two separate reference counting
mechanisms: the 'count' field in struct rose_neigh tracks references from
rose_node structures, while the 'use' field (now refcount_t) tracks
references from rose_sock.

This patch merges these two reference counting systems using 'use' field
for proper reference management. Specifically, this patch adds incrementing
and decrementing of rose_neigh->use when rose_neigh->count is incremented
or decremented.

This patch also modifies rose_rt_free(), rose_rt_device_down() and
rose_clear_route() to properly release references to rose_neigh objects
before freeing a rose_node through rose_remove_node().

These changes ensure rose_neigh structures are properly freed only when
all references, including those from rose_node structures, are released.
As a result, this resolves a slab-use-after-free issue reported by Syzbot.
CVSS Score: 5.5 (MEDIUM)
References: https://git.kernel.org/stable/c/384210cceb1873a4c8218b27ba[PII_REDACTED]b728; https://git.kernel.org/stable/c/4cce478c3e82a5fc788d72adb2f4c4e983997639; https://git.kernel.org/stable/c/9c547c8eee9d1cf6e744611d688b9f725cf9a115
CVE: CVE-2025-39829
Published: 2025-09-16
Description: In the Linux kernel, the following vulnerability has been resolved:

trace/fgraph: Fix the warning caused by missing unregister notifier

This warning was triggered during testing on v6.16:

notifier callback ftrace_suspend_notifier_call already registered
WARNING: CPU: 2 PID: 86 at kernel/notifier.c:23 notifier_chain_register+0x44/0xb0
...
Call Trace:
 <TASK>
 blocking_notifier_chain_register+0x34/0x60
 register_ftrace_graph+0x330/0x410
 ftrace_profile_write+0x1e9/0x340
 vfs_write+0xf8/0x420
 ? filp_flush+0x8a/0xa0
 ? filp_close+0x1f/0x30
 ? do_dup2+0xaf/0x160
 ksys_write+0x65/0xe0
 do_syscall_64+0xa4/0x260
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

When writing to the function_profile_enabled interface, the notifier was
not unregistered after start_graph_tracing failed, causing a warning the
next time function_profile_enabled was written.

Fixed by adding unregister_pm_notifier in the exception path.
CVSS Score: 5.5 (MEDIUM)
References: https://git.kernel.org/stable/c/000aa47a51233fd38a629b029478e0278e1e9fbe; https://git.kernel.org/stable/c/2a2deb9f8df[PII_REDACTED]1ac27041f19bb9e718b; https://git.kernel.org/stable/c/edede7a6dcd7435395cf757d053974aaab6ab1c2
CVE: CVE-2025-55109
Published: 2025-09-16
Description: An authentication bypass vulnerability exists in the out-of-support Control-M/Agent versions 9.0.18 to 9.0.20 and potentially earlier unsupported versions when using an empty or default kdb keystore or a default PKCS#12 keystore. A remote attacker with access to a signed third-party or demo certificate for client authentication can bypass the need for a certificate signed by the certificate authority of the organization during authentication on the Control-M/Agent.

The Control-M/Agent contains hardcoded certificates which are only trusted as fallback if an empty kdb keystore is used; they are never trusted if a PKCS#12 keystore is used. All of these certificates are now expired.


In addition, the Control-M/Agent default kdb and PKCS#12 keystores contain trusted third-party certificates (external recognized CAs and default self-signed demo certificates) which are trusted for client authentication.
CVSS Score: 9.0 (CRITICAL)
CWE: CWE-295
References: https://bmcapps.my.site.com/casemgmt/sc_KnowledgeArticle?sfdcid=000441963; https://bmcapps.my.site.com/casemgmt/sc_KnowledgeArticle?sfdcid=000442099
CVE: CVE-2025-55110
Published: 2025-09-16
Description: Control-M/Agents use a kdb or PKCS#12 keystore by default, and the default keystore password is well known and documented.

An attacker with read access to the keystore could access sensitive data using this password.
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-1392
References: https://bmcapps.my.site.com/casemgmt/sc_KnowledgeArticle?sfdcid=000441964; https://bmcapps.my.site.com/casemgmt/sc_KnowledgeArticle?sfdcid=000442099
CVE: CVE-2025-55111
Published: 2025-09-16
Description: Certain files with overly permissive permissions were identified in the out-of-support Control-M/Agent versions 9.0.18 to 9.0.20 and potentially earlier unsupported versions as well as in newer versions which were upgraded from an affected version. These files contain keys and passwords relating to SSL files, keystore and policies. An attacker with local access to the system running the Agent can access these files.
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-276
References: https://bmcapps.my.site.com/casemgmt/sc_KnowledgeArticle?sfdcid=000441965; https://bmcapps.my.site.com/casemgmt/sc_KnowledgeArticle?sfdcid=000442099
CVE: CVE-2025-55112
Published: 2025-09-16
Description: Out-of-support Control-M/Agent versions 9.0.18 to 9.0.20 (and potentially earlier unsupported versions) that are configured to use the non-default Blowfish cryptography algorithm use a hardcoded key. An attacker with access to network traffic and to this key could decrypt network traffic between the Control-M/Agent and Server.
CVSS Score: 7.4 (HIGH)
CWE: CWE-321, CWE-327
References: https://bmcapps.my.site.com/casemgmt/sc_KnowledgeArticle?sfdcid=000441966; https://bmcapps.my.site.com/casemgmt/sc_KnowledgeArticle?sfdcid=000442099
CVE: CVE-2025-55113
Published: 2025-09-16
Description: If the Access Control List is enforced by the Control-M/Agent and the C router is in use (default in Out-of-support Control-M/Agent versions 9.0.18 to 9.0.20 and potentially earlier unsupported versions; non-default but configurable using the JAVA_AR setting in newer versions), the verification stops at the first NULL byte encountered in the email address referenced in the client certificate. An attacker could bypass configured ACLs by using a specially crafted certificate.
CVSS Score: 9.0 (CRITICAL)
CWE: CWE-158
References: https://bmcapps.my.site.com/casemgmt/sc_KnowledgeArticle?sfdcid=000441967; https://bmcapps.my.site.com/casemgmt/sc_KnowledgeArticle?sfdcid=000442099
CVE: CVE-2025-55114
Published: 2025-09-16
Description: The improper order of AUTHORIZED_CTM_IP validation in the Control-M/Agent, where the Control-M/Server IP address is validated only after the SSL/TLS handshake is completed, exposes the Control-M/Agent to vulnerabilities in the SSL/TLS implementation under certain non-default conditions (e.g. CVE-2025-55117 or CVE-2025-55118) or potentially to resource exhaustion.
CVSS Score: 5.3 (MEDIUM)
CWE: CWE-696
References: https://bmcapps.my.site.com/casemgmt/sc_KnowledgeArticle?sfdcid=000441968; https://bmcapps.my.site.com/casemgmt/sc_KnowledgeArticle?sfdcid=000442099
CVE: CVE-2025-55115
Published: 2025-09-16
Description: A path traversal in the Control-M/Agent can lead to a local privilege escalation when an attacker has access to the system running the Agent. This vulnerability impacts the out-of-support Control-M/Agent versions 9.0.18 to 9.0.20 and potentially earlier unsupported versions. This vulnerability was fixed in 9.0.20.100 and above.
CVSS Score: 8.8 (HIGH)
CWE: CWE-23
References: https://bmcapps.my.site.com/casemgmt/sc_KnowledgeArticle?sfdcid=000441969; https://bmcapps.my.site.com/casemgmt/sc_KnowledgeArticle?sfdcid=000442099
CVE: CVE-2025-55116
Published: 2025-09-16
Description: A buffer overflow in the Control-M/Agent can lead to a local privilege escalation when an attacker has access to the system running the Agent.

This vulnerability impacts the out-of-support Control-M/Agent versions 9.0.18 to 9.0.20 and potentially earlier unsupported versions.
CVSS Score: 8.8 (HIGH)
CWE: CWE-121
References: https://bmcapps.my.site.com/casemgmt/sc_KnowledgeArticle?sfdcid=000441969; https://bmcapps.my.site.com/casemgmt/sc_KnowledgeArticle?sfdcid=000442099
CVE: CVE-2025-55117
Published: 2025-09-16
Description: A stack-based buffer overflow can be remotely triggered when formatting an error message in the Control-M/Agent when SSL/TLS communication is configured.


The issue occurs in the following cases:

  *  Control-M/Agent 9.0.20: SSL/TLS configuration is set to the non-default setting "use_openssl=n";
  *  Control-M/Agent 9.0.21 and 9.0.22: Agent router configuration uses the non-default settings "JAVA_AR=N" and "use_openssl=n".
CVSS Score: 5.3 (MEDIUM)
CWE: CWE-121
References: https://bmcapps.my.site.com/casemgmt/sc_KnowledgeArticle?sfdcid=000441972; https://bmcapps.my.site.com/casemgmt/sc_KnowledgeArticle?sfdcid=000442099
CVE: CVE-2025-55118
Published: 2025-09-16
Description: Memory corruptions can be remotely triggered in the Control-M/Agent when SSL/TLS communication is configured.


The issue occurs in the following cases:

  *  Control-M/Agent 9.0.20: SSL/TLS configuration is set to the non-default setting "use_openssl=n";
  *  Control-M/Agent 9.0.21 and 9.0.22: Agent router configuration uses the non-default settings "JAVA_AR=N" and "use_openssl=n"
CVSS Score: 8.9 (HIGH)
CWE: CWE-122, CWE-125, CWE-191, CWE-415, CWE-416
References: https://bmcapps.my.site.com/casemgmt/sc_KnowledgeArticle?sfdcid=000441972; https://bmcapps.my.site.com/casemgmt/sc_KnowledgeArticle?sfdcid=000442099
CVE: CVE-2025-55834
Published: 2025-09-16
Description: A Cross Site Scripting vulnerability in JeeWMS v.3.7 and before allows a remote attacker to obtain sensitive information via the logController.do component
CVSS Score: 6.1 (MEDIUM)
CWE: CWE-79
References: https://github.com/RrEeSeEeTt/CVEs/blob/main/JeeWMS-xss.md; https://github.com/RrEeSeEeTt/CVEs/blob/main/JeeWMS-xss.md
CVE: CVE-2025-7355
Published: 2025-09-16
Description: Authorization Bypass Through User-Controlled Key vulnerability in Beefull Energy Technologies Beefull App allows Exploitation of Trusted Identifiers.This issue affects Beefull App: before 24.07.2025.
CVSS Score: 6.5 (MEDIUM)
CWE: CWE-639
References: https://www.usom.gov.tr/bildirim/tr-25-0255
CVE: CVE-2024-12796
Published: 2025-09-16
Description: Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Holistic IT, Consultancy Coop. Workcube ERP allows Reflected XSS.This issue affects Workcube ERP: from V12 - V14 before Cognitive.
CVSS Score: 5.3 (MEDIUM)
CWE: CWE-79
References: https://www.usom.gov.tr/bildirim/tr-25-0256
CVE: CVE-2025-39830
Published: 2025-09-16
Description: In the Linux kernel, the following vulnerability has been resolved:

net/mlx5: HWS, Fix memory leak in hws_pool_buddy_init error path

In the error path of hws_pool_buddy_init(), the buddy allocator cleanup
doesn't free the allocator structure itself, causing a memory leak.

Add the missing kfree() to properly release all allocated memory.
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-401, CWE-401
References: https://git.kernel.org/stable/c/2c0a959bebdc1ada13cf9a8242f177c5400299e6; https://git.kernel.org/stable/c/86d13a6f49cb68aa91bd718b1b627e72e77285c1
CVE: CVE-2025-39832
Published: 2025-09-16
Description: In the Linux kernel, the following vulnerability has been resolved:

net/mlx5: Fix lockdep assertion on sync reset unload event

Fix lockdep assertion triggered during sync reset unload event. When the
sync reset flow is initiated using the devlink reload fw_activate
option, the PF already holds the devlink lock while handling unload
event. In this case, delegate sync reset unload event handling back to
the devlink callback process to avoid double-locking and resolve the
lockdep warning.

Kernel log:
WARNING: CPU: 9 PID: 1578 at devl_assert_locked+0x31/0x40
[...]
Call Trace:
<TASK>
 mlx5_unload_one_devl_locked+0x2c/0xc0 [mlx5_core]
 mlx5_sync_reset_unload_event+0xaf/0x2f0 [mlx5_core]
 process_one_work+0x222/0x640
 worker_thread+0x199/0x350
 kthread+0x10b/0x230
 ? __pfx_worker_thread+0x10/0x10
 ? __pfx_kthread+0x10/0x10
 ret_from_fork+0x8e/0x100
 ? __pfx_kthread+0x10/0x10
 ret_from_fork_asm+0x1a/0x30
</TASK>
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-667, CWE-667
References: https://git.kernel.org/stable/c/06d897148e[PII_REDACTED]0d851a69547b56b4be2e; https://git.kernel.org/stable/c/0c87dba9ccd3801d3b503f0b4fd41be343af4f06; https://git.kernel.org/stable/c/902a8bc23a24882200f57cadc270e15a2cfaf2bb
CVE: CVE-2025-39833
Published: 2025-09-16
Description: In the Linux kernel, the following vulnerability has been resolved:

mISDN: hfcpci: Fix warning when deleting uninitialized timer

With CONFIG_DEBUG_OBJECTS_TIMERS unloading hfcpci module leads
to the following splat:

[  250.215892] ODEBUG: assert_init not available (active state 0) object: ffffffffc01a3dc0 object type: timer_list hint: 0x0
[  250.217520] WARNING: CPU: 0 PID: 233 at lib/debugobjects.c:612 debug_print_object+0x1b6/0x2c0
[  250.218775] Modules linked in: hfcpci(-) mISDN_core
[  250.219537] CPU: 0 UID: 0 PID: 233 Comm: rmmod Not tainted 6.17.0-rc2-g6f713187ac98 #2 PREEMPT(voluntary)
[  250.220940] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
[  250.222377] RIP: 0010:debug_print_object+0x1b6/0x2c0
[  250.223131] Code: fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 75 4f 41 56 48 8b 14 dd a0 4e 01 9f 48 89 ee 48 c7 c7 20 46 01 9f e8 cb 84d
[  250.225805] RSP: 0018:ffff888015ea7c08 EFLAGS: 00010286
[  250.226608] RAX: [PII_REDACTED] RBX: [PII_REDACTED] RCX: ffffffff9be93a95
[  250.227708] RDX: 1ffff1100d945138 RSI: [PII_REDACTED] RDI: ffff88806ca289c0
[  250.228993] RBP: ffffffff9f014a00 R08: [PII_REDACTED] R09: ffffed1002bd4f39
[  250.230043] R10: ffff888015ea79cf R11: [PII_REDACTED] R12: [PII_REDACTED]
[  250.231185] R13: ffffffff9eea0520 R14: [PII_REDACTED] R15: ffff888015ea7cc8
[  250.232454] FS:  00007f3208f01540(0000) GS:ffff8880caf5a000(0000) knlGS:[PII_REDACTED]
[  250.233851] CS:  0010 DS: 0000 ES: 0000 CR0: [PII_REDACTED]
[  250.234856] CR2: 00007f32090a7421 CR3:[PII_REDACTED]d63000 CR4:[PII_REDACTED]0006f0
[  250.236117] Call Trace:
[  250.236599]  <TASK>
[  250.236967]  ? trace_irq_enable.constprop.0+0xd4/0x130
[  250.237920]  debug_object_assert_init+0x1f6/0x310
[  250.238762]  ? __pfx_debug_object_assert_init+0x10/0x10
[  250.239658]  ? __lock_acquire+0xdea/0x1c70
[  250.240369]  __try_to_del_timer_sync+0x69/0x140
[  250.241172]  ? __pfx___try_to_del_timer_sync+0x10/0x10
[  250.242058]  ? __timer_delete_sync+0xc6/0x120
[  250.242842]  ? lock_acquire+0x30/0x80
[  250.243474]  ? __timer_delete_sync+0xc6/0x120
[  250.244262]  __timer_delete_sync+0x98/0x120
[  250.245015]  HFC_cleanup+0x10/0x20 [hfcpci]
[  250.245704]  __do_sys_delete_module+0x348/0x510
[  250.246461]  ? __pfx___do_sys_delete_module+0x10/0x10
[  250.247338]  do_syscall_64+0xc1/0x360
[  250.247924]  entry_SYSCALL_64_after_hwframe+0x77/0x7f

Fix this by initializing hfc_tl timer with DEFINE_TIMER macro.
Also, use mod_timer instead of manual timeout update.
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-908, CWE-908
References: https://git.kernel.org/stable/c/43fc5da8133badf17f5df250ba03b9d882254845; https://git.kernel.org/stable/c/97766512a9951b9fd6fc97f1b93211642bb0b220
CVE: CVE-2025-39834
Published: 2025-09-16
Description: In the Linux kernel, the following vulnerability has been resolved:

net/mlx5: HWS, Fix memory leak in hws_action_get_shared_stc_nic error flow

When an invalid stc_type is provided, the function allocates memory for
shared_stc but jumps to unlock_and_out without freeing it, causing a
memory leak.

Fix by jumping to free_shared_stc label instead to ensure proper cleanup.
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-401, CWE-401
References: https://git.kernel.org/stable/c/051fd8576a2e4e95d5870c5c9f8679c5b16882e4; https://git.kernel.org/stable/c/a630f83592cdad1253523a1b760cfe78fef6cd9c
CVE: CVE-2025-39835
Published: 2025-09-16
Description: In the Linux kernel, the following vulnerability has been resolved:

xfs: do not propagate ENODATA disk errors into xattr code

ENODATA (aka ENOATTR) has a very specific meaning in the xfs xattr code;
namely, that the requested attribute name could not be found.

However, a medium error from disk may also return ENODATA. At best,
this medium error may escape to userspace as "attribute not found"
when in fact it's an IO (disk) error.

At worst, we may oops in xfs_attr_leaf_get() when we do:

	error = xfs_attr_leaf_hasname(args, &bp);
	if (error == -ENOATTR)  {
		xfs_trans_brelse(args->trans, bp);
		return error;
	}

because an ENODATA/ENOATTR error from disk leaves us with a null bp,
and the xfs_trans_brelse will then null-deref it.

As discussed on the list, we really need to modify the lower level
IO functions to trap all disk errors and ensure that we don't let
unique errors like this leak up into higher xfs functions - many
like this should be remapped to EIO.

However, this patch directly addresses a reported bug in the xattr
code, and should be safe to backport to stable kernels. A larger-scope
patch to handle more unique errors at lower levels can follow later.

(Note, prior to 07120f1abdff we did not oops, but we did return the
wrong error code to userspace.)
CVSS Score: 7.8 (HIGH)
References: https://git.kernel.org/stable/c/157ddfb05961c68ab7d457a462822a698e4e4bf4; https://git.kernel.org/stable/c/39fc2742ca14f7fbc621ce9b43bcbd00248cb9a8; https://git.kernel.org/stable/c/90bae69c2959c39912f0c2f07a9a7894f3fc49f5
CVE: CVE-2025-39836
Published: 2025-09-16
Description: In the Linux kernel, the following vulnerability has been resolved:

efi: stmm: Fix incorrect buffer allocation method

The communication buffer allocated by setup_mm_hdr() is later on passed
to tee_shm_register_kernel_buf(). The latter expects those buffers to be
contiguous pages, but setup_mm_hdr() just uses kmalloc(). That can cause
various corruptions or BUGs, specifically since commit 9aec2fb0fd5e
("slab: allocate frozen pages"), though it was broken before as well.

Fix this by using alloc_pages_exact() instead of kmalloc().
CVSS Score: 7.8 (HIGH)
CWE: CWE-787, CWE-787
References: https://git.kernel.org/stable/c/630c0e6064daf84f17aad1a7d9ca76b562e3fe47; https://git.kernel.org/stable/c/77ff27ff0e4529a003c8a1c2492c111968c378d3; https://git.kernel.org/stable/c/c5e81e672699e0c5557b2b755cc8f7a69aa92bff
CVE: CVE-2025-44034
Published: 2025-09-16
Description: SQL injection vulnerability in oa_system oasys v.1.1 allows a remote attacker to execute arbitrary code via the alph parameters in src/main/Java/cn/gson/oasys/controller/address/AddrController
CVSS Score: 8.0 (HIGH)
CWE: CWE-89
References: https://github.com/qkdjksfkeg/Security-Collections/blob/main/sqlinjection2.md
CVE: CVE-2025-52044
Published: 2025-09-16
Description: In Frappe ERPNext v15.57.5, the function get_stock_balance() at erpnext/stock/utils.py is vulnerable to SQL Injection, which allows an attacker to extract all information from databases by injecting SQL query into inventory_dimensions_dict parameter.
CVSS Score: 7.5 (HIGH)
CWE: CWE-89
References: https://github.com/Vietsunshine-Electronic-Solution-JSC/Vulnerability-Disclosures/blob/main/2025/Frappe%20Framework%20-%20Multiple%20SQL%20Injection.md; https://github.com/frappe/erpnext/pull/49192/commits/eb22794f14351c2ff5731548c48bef0b91765c86
CVE: CVE-2025-56276
Published: 2025-09-16
Description: code-projects Food Ordering Review System 1.0 is vulnerable to Cross Site Scripting (XSS) in the registration function. An attacker enters malicious JavaScript code as a username, which triggers the XSS vulnerability when the admin views user information, resulting in the disclosure of the admin's cookie information.
CVSS Score: 5.4 (MEDIUM)
CWE: CWE-79
References: https://code-projects.org/food-ordering-review-system-in-php-with-source-code/; https://github.com/Chen1-Boop/CVE/blob/main/CVE-2025-56276.md; https://github.com/Chen1-Boop/CVE/blob/main/CVE-2025-56276.md
CVE: CVE-2025-57119
Published: 2025-09-16
Description: An issue in Online Library Management System v.3.0 allows an attacker to escalate privileges via the adminlogin.php component and the Login function
CVSS Score: 9.8 (CRITICAL)
CWE: CWE-250
References: http://online.com; https://github.com/Jazeye/CVE/blob/main/CVE-2025-57119/README.md; https://github.com/danielmiessler/SecLists/blob/master/Usernames/cirt-default-usernames.txt
CVE: CVE-2025-8057
Published: 2025-09-16
Description: Authorization Bypass Through User-Controlled Key, Externally Controlled Reference to a Resource in Another Sphere, Improper Authorization vulnerability in Patika Global Technologies HumanSuite allows Exploiting Trust in Client.This issue affects HumanSuite: before 53.21.0.
CVSS Score: 6.5 (MEDIUM)
CWE: CWE-285, CWE-610, CWE-639
References: https://www.usom.gov.tr/bildirim/tr-25-0257
CVE: CVE-2025-8276
Published: 2025-09-16
Description: Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting'), Improper Encoding or Escaping of Output, Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in Patika Global Technologies HumanSuite allows Cross-Site Scripting (XSS), Phishing.This issue affects HumanSuite: before 53.21.0.
CVSS Score: 4.3 (MEDIUM)
CWE: CWE-74, CWE-79, CWE-116
References: https://www.usom.gov.tr/bildirim/tr-25-0257