11821 matches found
CVE-2025-59943
CVE-2025-59943 affects phpMyFAQ prior to 4.0.13. Versions 4.0-nightly-2025-10-03 and earlier fail to enforce unique email addresses during user registration, allowing multiple distinct accounts to share the same email. This can cause account ambiguity and, in certain configurations, may lead to p...
GHSA-9WJ2-4HCM-R74J phpMyFAQ duplicate email registration allows multiple accounts with the same email
Summary phpMyFAQ does not enforce uniqueness of email addresses during user registration. This allows multiple distinct accounts to be created with the same email. Because email is often used as an identifier for password resets, notifications, and administrative actions, this flaw can cause...
phpMyFAQ duplicate email registration allows multiple accounts with the same email
Summary phpMyFAQ does not enforce uniqueness of email addresses during user registration. This allows multiple distinct accounts to be created with the same email. Because email is often used as an identifier for password resets, notifications, and administrative actions, this flaw can cause...
CVE-2025-9892
The Restrict User Registration plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.1. This is due to missing or incorrect nonce validation on the update function. This makes it possible for unauthenticated attackers to update the plugin's...
CVE-2025-9892 Restrict User Registration <= 1.0.1 - Cross-Site Request Forgery to Settings Update
The Restrict User Registration plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.1. This is due to missing or incorrect nonce validation on the update function. This makes it possible for unauthenticated attackers to update the plugin's...
EUVD-2025-32263
The Restrict User Registration plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.1. This is due to missing or incorrect nonce validation on the update function. This makes it possible for unauthenticated attackers to update the plugin's...
CVE-2025-9892 Restrict User Registration <= 1.0.1 - Cross-Site Request Forgery to Settings Update
The Restrict User Registration plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.1. This is due to missing or incorrect nonce validation on the update function. This makes it possible for unauthenticated attackers to update the plugin's...
CVE-2025-9892
CVE-2025-9892 describes a Cross-Site Forgery vulnerability in the WordPress plugin Restrict User Registration (versions ≤ 1.0.1) due to missing nonce validation in the update() function. This allows unauthenticated attackers to update plugin settings by misleading an admin into performing an act...
SUSE CVE-2022-50468
In the Linux kernel, the following vulnerability has been resolved: platform/chrome: crosusbpdnotify: Fix error handling in crosusbpdnotifyinit The following WARNING message was given when rmmod crosusbpdnotify: Unexpected driver unregister! WARNING: CPU: 0 PID: 253 at drivers/base/driver.c:270...
PT-2025-40540
Name of the Vulnerable Software and Affected Versions phpMyFAQ versions 4.0-nightly-2025-10-03 and below Description phpMyFAQ does not enforce uniqueness of email addresses during user registration, allowing multiple distinct accounts to be created with the same email. This can cause account...
WordPress plugin Restrict User Registration 跨站请求伪造漏洞
WordPress and WordPress plugin are both products of the WordPress Foundation.WordPress is a blogging platform developed in the PHP language. The platform has the ability to host personal blog sites on PHP and MySQL based servers.WordPress plugin is an application plugin. A cross-site request...
SUSE CVE-2022-50434
In the Linux kernel, the following vulnerability has been resolved: blk-mq: fix possible memleak when register 'hctx' failed There's issue as follows when do fault injection test: unreferenced object 0xffff888132a9f400 size 512: comm "insmod", pid 308021, jiffies 4324277909 age 509.733s hex dump...
CVE-2022-50468
In the Linux kernel, the following vulnerability has been resolved: platform/chrome: crosusbpdnotify: Fix error handling in crosusbpdnotifyinit The following WARNING message was given when rmmod crosusbpdnotify: Unexpected driver unregister! WARNING: CPU: 0 PID: 253 at drivers/base/driver.c:270...
CVE-2022-50449
In the Linux kernel, the following vulnerability has been resolved: clk: samsung: Fix memory leak in samsungclkregisterpll If clkregister fails, @pll-ratetable may have allocated memory by kmemdup, so it needs to be freed, otherwise will cause memory leak issue, this patch fixes it...
CVE-2022-50427
In the Linux kernel, the following vulnerability has been resolved: ALSA: ac97: fix possible memory leak in sndac97devregister If deviceregister fails in sndac97devregister, it should call putdevice to give up reference, or the name allocated in devsetname is leaked...
UBUNTU-CVE-2022-50449
In the Linux kernel, the following vulnerability has been resolved: clk: samsung: Fix memory leak in samsungclkregisterpll If clkregister fails, @pll-ratetable may have allocated memory by kmemdup, so it needs to be freed, otherwise will cause memory leak issue, this patch fixes it...
CVE-2022-50468 platform/chrome: cros_usbpd_notify: Fix error handling in cros_usbpd_notify_init()
In the Linux kernel, the following vulnerability has been resolved: platform/chrome: crosusbpdnotify: Fix error handling in crosusbpdnotifyinit The following WARNING message was given when rmmod crosusbpdnotify: Unexpected driver unregister! WARNING: CPU: 0 PID: 253 at drivers/base/driver.c:270...
CVE-2022-50449 clk: samsung: Fix memory leak in _samsung_clk_register_pll()
In the Linux kernel, the following vulnerability has been resolved: clk: samsung: Fix memory leak in samsungclkregisterpll If clkregister fails, @pll-ratetable may have allocated memory by kmemdup, so it needs to be freed, otherwise will cause memory leak issue, this patch fixes it...
CVE-2022-50434 blk-mq: fix possible memleak when register 'hctx' failed
In the Linux kernel, the following vulnerability has been resolved: blk-mq: fix possible memleak when register 'hctx' failed There's issue as follows when do fault injection test: unreferenced object 0xffff888132a9f400 size 512: comm "insmod", pid 308021, jiffies 4324277909 age 509.733s hex dump...