OpenClaw versions prior to 2026.2.21 fail to filter dangerous process-control environment variables from config env.vars, allowing startup-time code execution. Attackers can inject variables like NODE_OPTIONS or LD_* through configuration to execute arbitrary code in the OpenClaw gateway service runtime context.
Vulnogram 1.0.0 contains a stored cross-site scripting vulnerability in comment hypertext handling that allows attackers to inject malicious scripts. Remote attackers can inject XSS payloads through comments to execute arbitrary JavaScript in victims' browsers.
openDCIM version 23.04, through commit 4467e9c4, contains an OS command injection vulnerability in report_network_map.php. The application retrieves the 'dot' configuration parameter from the database and passes it directly to exec() without validation or sanitization. If an attacker can modify the fac_Config.dot value, arbitrary commands may be executed in the context of the web server process.
openDCIM version 23.04, through commit 4467e9c4, contains a SQL injection vulnerability in Config::UpdateParameter. The install.php and container-install.php handlers pass user-supplied input directly into SQL statements using string interpolation without prepared statements or proper input sanitation. An authenticated user can execute arbitrary SQL statements against the underlying database.
openDCIM version 23.04, through commit 4467e9c4, contains a missing authorization vulnerability in install.php and container-install.php. The installer and upgrade handler expose LDAP configuration functionality without enforcing application role checks. Any authenticated user can access this functionality regardless of assigned privileges. In deployments where REMOTE_USER is set without authentication enforcement, the endpoint may be accessible without credentials. This allows unauthorized modification of application configuration.
OpenSIPS versions 3.1 before 3.6.4 containing the auth_jwt module (prior to commit 3822d33) contain a SQL injection vulnerability in the jwt_db_authorize() function in modules/auth_jwt/authorize.c when db_mode is enabled and a SQL database backend is used. The function extracts the tag claim from a JWT without prior signature verification and incorporates the unescaped value directly into a SQL query. An attacker can supply a crafted JWT with a malicious tag claim to manipulate the query result and bypass JWT authentication, allowing impersonation of arbitrary identities.
GetSimpleCMS Community Edition (CE) versions prior to 3.3.22 (3.3.16 tested) contains a stored cross-site scripting (XSS) vulnerability in the Theme to Components functionality within components.php. User-supplied input provided to the "slug" field of a component is stored without proper output encoding. While other fields are sanitized using safe_slash_html(), the slug parameter is written to XML and later rendered in the administrative interface without sanitation, resulting in persistent execution of arbitrary JavaScript. An authenticated administrator can inject malicious script content that executes whenever the affected Components page is viewed by any authenticated user, enabling session hijacking, unauthorized administrative actions, and persistent compromise of the CMS administrative interface.
Chainlit versions prior to 2.9.4 contain a server-side request forgery (SSRF) vulnerability in the /project/element update flow when configured with the SQLAlchemy data layer backend. An authenticated client can provide a user-controlled url value in an Element, which is fetched by the SQLAlchemy element creation logic using an outbound HTTP GET request. This allows an attacker to make arbitrary HTTP requests from the Chainlit server to internal network services or cloud metadata endpoints and store the retrieved responses via the configured storage provider.
Chainlit versions prior to 2.9.4 contain an arbitrary file read vulnerability in the /project/element update flow. An authenticated client can send a custom Element with a user-controlled path value, causing the server to copy the referenced file into the attacker’s session. The resulting element identifier (chainlitKey) can then be used to retrieve the file contents via /project/file/<chainlitKey>, allowing disclosure of any file readable by the Chainlit service.
Cowrie versions prior to 2.9.0 have a server-side request forgery (SSRF) vulnerability in the emulated shell commands wget and curl. These commands perform real outbound HTTP requests to attacker-supplied destinations without rate limiting, allowing unauthenticated attackers to generate unbounded HTTP traffic toward arbitrary third-party targets. This can be abused to amplify denial-of-service attacks and mask the attacker's true source IP behind the honeypot's IP.
A stack-based buffer overflow vulnerability exists in libcoap versions up to and including 4.3.5 in the address resolution code when proxy logic is enabled. This occurs due to copying attacker-controlled hostname data into a fixed 256-byte stack buffer without proper bounds checking. A remote attacker can cause a crash and potentially achieve remote code execution depending on compiler and runtime protections.
A vulnerability in weDevs WP Project Manager up to version 3.0.1 allows insertion of sensitive information into sent data, potentially exposing embedded sensitive data to unauthorized parties. The flaw is identified as CWE-201 and has a CVSS 3.1 score of 6.5, indicating a medium severity impact primarily affecting confidentiality. The vulnerability requires low privileges and no user interaction for exploitation over a network. No public exploit or known in-the-wild exploitation has been reported. No patch or remediation information is currently available.
The npm package 'cici-bakwan60-sukiwir' is part of a malicious campaign linked to the tea.xyz token reward scheme. It contains autopublish scripts that automatically generate and publish derivative packages with randomized Indonesian-themed names. The payload modifies package.json files to remove private flags and changes version numbers, enabling continuous republishing of variants. This behavior pollutes the npm registry and inflates developer reputation scores fraudulently.
The npm package chubby_raccoon_z3n is part of a malicious campaign linked to tea.xyz token rewards. It contains autopublish scripts that automatically generate and publish derivative packages with randomized Indonesian-themed names. The payload modifies package.json files to remove private flags and change version numbers, enabling continuous republishing of variants. This behavior pollutes the npm registry and inflates developer reputation scores fraudulently.
The npm package chubby_primate_z3n is part of a malicious campaign linked to tea.xyz token rewards. It contains autopublish scripts that automatically generate and publish derivative packages with randomized Indonesian-themed names. The payload modifies package.json files to remove private flags and changes version numbers, enabling continuous republishing of variants. This activity pollutes the npm registry and inflates developer reputation scores fraudulently.
The npm package christian_silverfish_z3n is part of a malicious campaign linked to tea.xyz token rewards. It contains autopublish scripts that automatically generate and publish derivative packages with randomized names to inflate developer reputation scores. The payload modifies package.json files to remove private flags, alters version numbers, and continuously republishes variants with Indonesian-themed names, polluting the npm registry.
The christian_rook_z3n npm package is part of a malicious campaign linked to tea.xyz token rewards. It contains autopublish scripts that automatically generate and publish derivative packages with randomized Indonesian-themed names. The payload modifies package.json files to remove private flags and change version numbers, enabling continuous republishing of variants. This activity pollutes the npm registry and inflates developer reputation scores fraudulently.
The npm package christian_caribou_z3n is part of a malicious campaign linked to tea.xyz token rewards. It contains autopublish scripts that automatically generate and publish derivative packages with randomized Indonesian-themed names. The payload modifies package.json files to remove private flags and change version numbers, enabling continuous republishing of variants. This activity pollutes the npm registry and inflates developer reputation scores fraudulently.
The chosen_firefly_z3n npm package is part of a malicious campaign linked to tea.xyz token rewards. It contains autopublish scripts that automatically generate and publish derivative packages with randomized Indonesian-themed names. The payload modifies package.json files to remove private flags and change version numbers, enabling continuous republishing of variants. This activity pollutes the npm registry and inflates developer reputation scores fraudulently.
The charming_tortoise_z3n npm package is part of a malicious campaign linked to tea.xyz token rewards. It contains autopublish scripts that automatically generate and publish derivative packages with randomized names. The payload modifies package.json files to remove private flags, alters version numbers, and creates Indonesian-themed package names. This behavior leads to continuous republishing of variants, polluting the npm registry.