GLPI versions 10.0.0 before 10.0.28 and 11.0.0 before 11.0.10 contain a privilege escalation vulnerability. Authenticated users with the Technician profile can clone Super-Admin accounts due to improper privilege management in the cloning function, resulting in unauthorized elevated access.
Froxlor versions from 2.3.8 up to but not including 2.3.15 contain an information disclosure vulnerability. This flaw allows administrators with the customers_see_all permission to view all accounts' API keys and secrets due to an unscoped database query in api_keys.php. Exploitation enables reading the super administrator's API key and secret, which can be replayed to gain super administrator control. The issue is fixed in version 2.3.15.
Jpom versions 2.10.0 through 2.11.12 contain an authentication bypass vulnerability that allows unauthenticated attackers to gain super-administrator access by injecting specially crafted query conditions into the JPOM-USER-TOKEN header. This occurs because the Hutool Condition parser interprets injected values like 'is not null' as operators, enabling command execution through Jpom's script features.
A vulnerability in the Security Plugin, Firewall & Malware Scanner with Auto Removal WordPress plugin before version 2.191 allows non-super-admin administrators, including subsite administrators on multisite WordPress installations, to read sensitive tracked files. This exposure includes critical information such as the main configuration file, authentication keys, salts, and database credentials. The flaw arises because the plugin does not restrict its File System Watcher file viewer to super admins or limit it to legitimately tracked files.
A race condition vulnerability in the Linux kernel's btrfs filesystem was addressed by protecting the sb_write_pointer() function with the mapping invalidate lock. This function reads the super block from the block device page cache and previously had a race condition related to block size changes. The fix serializes the read operation against block size changes to prevent inconsistent reads.
A privilege management vulnerability in the User Profile Builder WordPress plugin before version 4.0.5 allows an Administrator of a Multisite subsite to edit any user's account email via the front-end Edit Profile form. This includes the ability to change a Network Super Admin's email and potentially take over that account through the password-reset process.
The Grav Flex Objects plugin versions 1.4.0 through 1.4.16 contain an authorization bypass vulnerability. The issue arises because the API routes under /api/v1/flex-objects/pages only verify directory-level admin.pages permissions but do not enforce the more granular Pages API permissions such as api.pages.read/write or page-level permissions. This allows authenticated users with api.access and admin.pages or admin.configuration.pages permissions, but who are not super users, to read, modify, or delete pages they should not have access to.
Apache Pulsar contains a missing authorization vulnerability in its Pulsar Functions worker REST API. Specifically, the deprecated functions connectors endpoints allow any authenticated user to read the catalog of installed Pulsar IO connectors without requiring super-user access, even when authorization is enabled. This exposure is limited to metadata disclosure of connector type definitions and does not allow modification or management of connectors. The issue affects versions from 2.4.1 before 4.0.14 and from 4.1.0 before 4.2.5. Fixed versions require super-user access for these endpoints, aligning with the worker connectors endpoint's authorization checks.
Apache Pulsar's MultiRolesTokenAuthorizationProvider improperly authorizes clients based on unverified JSON Web Tokens (JWTs) when anonymousUserRole is set and fallback authentication is allowed. This flaw allows unauthenticated clients to present forged or unsigned tokens with arbitrary roles, potentially gaining super-user access to administrative functions without valid credentials. The issue affects HTTP and WebSocket APIs but not the Pulsar binary protocol. It impacts Apache Pulsar versions from 2.8.1 before 4.0.14 and from 4.1.0 before 4.2.5.
US agencies NIST, CISA, and NSA have published a set of ten voluntary incident response practices aimed at managing rogue AI (super intelligence) agent incidents. These practices cover five stages: prepare, detect, respond, recover, and report, providing a comprehensive framework for organizations to handle unexpected or unauthorized AI agent behavior. The guidance emphasizes preparation activities like asset inventories and zero-trust controls, continuous monitoring for anomalies, effective response including isolation and root cause analysis, tested recovery procedures, and thorough reporting including legal notifications and public information sharing. The document serves as a clear checklist rather than introducing new governance concepts, helping organizations maintain stable and secure AI agent operations.
DB-GPT through 0.8.2 contains a hardcoded credentials vulnerability in its default docker-compose.yml that sets a static MYSQL_ROOT_PASSWORD and publishes port 3306 on all interfaces. Attackers reaching port 3306 or the shared dbgptnet network can authenticate as root@% to gain full database access including FILE and SUPER privileges.
FlyCms version 0 contains a default credentials vulnerability allowing unauthenticated remote attackers to gain super administrator access using the default username 'flycms' and password 'admin123'. Exploitation requires only solving an image captcha via the login API endpoint, enabling full control over site content, users, and configuration.
phpMyFAQ versions 3.2.0 before 4.0.0 and 4.0.2 before 4.2.0-beta contain an authentication bypass vulnerability in the Microsoft Entra ID login flow. The issue arises because the system links users by the mutable preferred_username claim and the AuthEntraId::create() function ignores duplicate-login exceptions, allowing attackers controlling an Entra identity with a matching preferred_username to take over local accounts, including super-admin accounts.
LangChat through commit 2a6285a has a critical missing authentication vulnerability that allows unauthenticated remote attackers to access REST controllers. Due to the absence of a Sa-Token interceptor, attackers can query sensitive endpoints such as /api/v1/auth/users to read plaintext passwords, retrieve LLM provider API keys, create super-admin accounts, and modify or delete data.