phpMyFAQ 3.2.5 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an authorization bypass vulnerability in the user/request-removal API endpoint that lets authenticated users file account removal requests as other users. The ownership check calls getUserById() with the attacker-supplied userId on the session user object, so it compares the input against the target's own record. Attackers who know a victim's login name and email can submit that userId, loginname, and email, sending administrators a spoofed Remove User Request email. This may lead an admin to delete the victim's account and data.
PMail 2.5.0 through 2.9.8 contains a stored cross-site scripting vulnerability that allows authenticated users to inject scripts by sending unsanitized HTML through /api/email/send. Attackers can embed event-handler payloads like img onerror that execute when administrators view the message, enabling privileged API calls such as password changes for account takeover.
SEPPmail Secure Email Gateway versions before 15.1.1 have a weakness in the password recovery mechanism for unregistered GINA accounts with empty initial passwords. This flaw allows a remote unauthenticated attacker to reset the password of such an account without proper ownership verification, enabling unauthorized access and denial of service to the legitimate user.
SEPPmail Secure Email Gateway (SEG) versions prior to 15.1.1 contain an LDAP injection vulnerability in the GINA web interface. This flaw arises because the software does not properly neutralize LDAP metacharacters in an unauthenticated account-selection input. A remote attacker without authentication can exploit this to enumerate email addresses.
An IDOR vulnerability in DJ-Classifieds Joomla extension versions prior to 3.11.3 allows any logged-in user to access full content of other users' ads, including private details like phone number, address, email, and price. This occurs because the 'duplicate my ad' feature loads ads by numeric ID without verifying ownership or publication status.
In June 2026, iRhythm, a medical equipment provider specializing in wearable cardiac monitors, suffered a data breach impacting over 8.1 million individuals. Hackers accessed personal information and iRhythm account and device data from third-party-hosted business applications and attempted to extort a ransom. The compromised data includes names, addresses, dates of birth, email addresses, phone numbers, and device-related identifiers. iRhythm has not found evidence of identity theft or impact on its medical devices or operations. Notifications have been sent to affected individuals and regulatory bodies, including the US Department of Health and Human Services.
The Waline login endpoint in @waline/vercel before version 1.41.0 accepts a non-string email value, which leads to a MongoDB query filter that matches all users. This causes the login process to verify the submitted password against the first-registered user (the administrator) without requiring the correct email. This vulnerability enables partial authentication bypass, user enumeration, and credential-stuffing amplification against the administrator account.
A vulnerability in better-auth versions from 1.5.0-beta.12 up to but not including 1.7.7 with the OAuth Proxy plugin allows an attacker to sign in as another user if certain conditions are met. The issue arises when the OAuth Proxy plugin shares the same secret as the global Better Auth secret, sign-in state is stored in a cookie, and implicit account linking is enabled. An attacker who knows a user's verified email can impersonate that user without needing provider sign-in or victim interaction. The flaw is fixed in version 1.7.7.
Aokigahara is an infostealer malware targeting traditional data sources such as browsers, VPN clients, cryptocurrency wallets, FTP/SFTP clients, password managers, and email applications. It uniquely targets AI applications and development tools, stealing authentication files, session data, and configuration files from services like Claude, ChatGPT Desktop, Codex, and GitHub Copilot. It also collects developer credentials including Git files, SSH private keys, and cloud service credentials (AWS, Azure, Google Cloud). The stolen AI credentials may be used for unauthorized access, account resale, or data extortion. The malware uses anti-analysis techniques and secures its command-and-control communications with AES-256 encryption and X25519 key exchange.
phpMyFAQ versions before 4.1.9 and between 4.2.0-alpha and 4.2.0-beta contain an account enumeration vulnerability. This flaw allows unauthenticated attackers to confirm registered display names and emails by observing distinct HTTP 409 responses when submitting guest comments. The vulnerability can be exploited to link user names to email addresses, facilitating targeted phishing attacks.
### **Impact**
An unauthenticated attacker who knows an account’s email address or username could trigger Payload’s account lockout mechanism and prevent that user from signing in.
You are affected if:
* Using an affected Payload version with an auth-enabled collection that uses local authentication and account lockout.
Applications that do not use Payload local authentication are not affected.
### **Patches**
Successful password resets now clear the account’s lockout state. The forgot-password flow also enforces a configurable minimum interval between reset emails, which defaults to 15 seconds.
Users should upgrade Payload packages to `>= 3.90.0` or `>= 4.0.0-canary.34`.
The Simple Membership plugin for WordPress is vulnerable to unauthorized modification of data and sensitive information disclosure in versions up to, and including, 4.8.3 via the resend-activation and email-activation endpoints. The endpoints are dispatched from SwpmInitTimeTasks::check_and_do_email_activation() on frontend init with no authentication, nonce, capability, or ownership check, and the recipient address used by SwpmRegistration::send_reg_email() is taken from an attacker-controlled $_POST['email'] parameter (overriding the member's registered address). This makes it possible for unauthenticated attackers to redirect an arbitrary pending member's activation email — and the follow-up 'registration complete' email containing the member's username and plaintext password — to an attacker-chosen address, and to then activate that member's account without their consent.
This report summarizes multiple cybersecurity developments including a set of iCloud email spoofing vulnerabilities, phishing campaigns targeting AI policy experts, a Chrome adblocker extension spying on AI chat conversations, and a large batch of vulnerabilities patched by Kiteworks. The iCloud spoofing bugs allowed attackers to send emails from arbitrary icloud.com addresses that passed SPF, DKIM, and DMARC checks due to inconsistent mail header parsing. The phishing campaigns involved a China-aligned group using fake AI advisory committee invitations to steal credentials via an adversary-in-the-middle proxy. The Poper Blocker Chrome extension was found to collect users' browsing history and AI chat conversations stealthily. Kiteworks patched over 100 vulnerabilities, including critical bugs that could lead to account takeover and code execution. Additional highlights include AI-assisted discovery of Android app flaws and a Cloudflare Containers data leakage vulnerability that was patched. No active exploits in the wild were reported for these issues.
HomeBox is a home inventory and organization system. Prior to 0.26.0, POST /v1/groups/members invokes HandleGroupMemberAdd and GroupService.AddMember using a caller-supplied userID without requiring an owner role, an invitation token, target-user consent, or target-user notification. Any authenticated user can force another account into the caller's group, disclose the target user's email address and name through the resulting member list, and create the membership prerequisite used by a separate cross-group inventory-wipe vulnerability. This issue is fixed in version 0.26.0.
The Really Simple Security WordPress plugin before 9.8.1 does not prevent an unauthenticated request from resetting an account's completed email two-factor enrolment, allowing an attacker who already knows the account's password to bypass the second factor and obtain that user's session, up to administrator.
SEPPmail Secure Email Gateway versions before 15.0.7 have an improper authentication vulnerability where a fully privileged session is created before multi-factor authentication (MFA) enrollment is completed. This allows an attacker who knows the password of an MFA-required but unenrolled account to access protected functionality without providing the second factor.
Filament is a collection of full-stack components for accelerated Laravel development. From 4.0.0 until 4.12.5 and 5.7.5, packages/panels/src/Auth/Pages/Login.php presents the multi-factor authentication challenge before evaluating canAccessPanel(). For an account that canAccessPanel() denies, submitting the correct password renders the MFA challenge while an incorrect password returns the generic authentication failure, allowing an unauthenticated attacker to confirm whether a candidate password is valid for that account. When email-based MFA is configured, the correct-password path also sends a login code to the account holder. The issue applies only to accounts that have MFA enabled and are denied panel access. Authentication is not bypassed because canAccessPanel() still runs after the challenge, and no session is created. This issue is fixed in versions 4.12.5 and 5.7.5.
Filament is a collection of full-stack components for accelerated Laravel development. From 4.0.0 until 4.12.6 and 5.7.6, packages/panels/src/Auth/MultiFactor/App/AppAuthentication.php uses AppAuthentication::verifyCode() with a used-code cache key derived from both the app authentication secret and the submitted TOTP code. This isolates the newest accepted timestep by code instead of by secret, allowing a previously issued app-based MFA code to be accepted after a newer code has already been used. Reuse of the exact same code was already prevented, but another code inside the accepted time window remained usable. An attacker who obtains the target account's password and one app-based MFA code can use that code for the remainder of the configured window, which is approximately four minutes with the default settings, even after the legitimate account holder logs in with a newer code. Email-based MFA is not affected. This issue is fixed in versions 4.12.6 and 5.7.6.