CWE-470
Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')
Monthly
Remote code execution affects PaperCut MF and PaperCut NG through unsafe dynamic class loading in the database connection utilities, which instantiate JDBC driver classes from configurable driver names without validating them against an allowlist. An attacker who can control administrative system configuration parameters can force the server to load and execute arbitrary Java bytecode already present on the application classpath, running with the full privileges of the PaperCut server process. No public exploit identified at time of analysis, but the PR:H requirement and PaperCut's history of being targeted make prompt patching advisable.
Arbitrary PHP constructor execution is possible through the MailPreview feature of CakePHP debug_kit due to unsafe reflection (CWE-470), affecting all 4.x versions below 4.10.3 and 5.x versions below 5.2.4. An attacker with low-privileged network access to an application running in debug mode on a local or allowlisted hostname can pass a fully-qualified PHP class name as the previewName parameter, causing the controller to instantiate arbitrary classes. Vendor-released patches 4.10.3 and 5.2.4 address this issue; no public exploit has been identified at time of analysis.
Unsafe dynamic class instantiation in Vocos allows arbitrary code execution when a user loads a model from an attacker-controlled Hugging Face repository. The library's `Vocos.from_pretrained` fetches a remote `config.yaml` from a caller-supplied repository and passes it directly to `instantiate_class`, which imports and calls any Python callable named in the configuration without an allowlist. Any user who loads a Vocos model from a repository they do not fully trust is exposed to full code execution in their Python process. No public exploit has been identified at time of analysis, but the attack path requires minimal sophistication given the direct code path from remote config to `__import__`/`getattr`/call.
Unvalidated Class.forName() with initialization enabled in RabbitMQ Java Client's JSON-RPC tooling allows a network-positioned attacker to trigger arbitrary static initializers in the victim JVM. Applications using com.rabbitmq:amqp-client before 5.33.0 that employ the JsonRpcClient class are exposed when an attacker can control or spoof the system.describe broker response - either as a co-tenant on a shared broker or via network interception. Successful exploitation achieves code-like effects through static initializer execution and a secondary type-confusion path via mapper.parse, with full confidentiality, integrity, and availability impact on the client process. No public exploit identified at time of analysis, and this CVE is not listed in CISA KEV.
JEXL expression sandbox bypass in OpenNMS Meridian and Horizon allows a low-privileged authenticated user to load arbitrary Java classes on the server via the Measurements REST API, enabling confidentiality disclosure and integrity compromise. The flaw stems from incorrect authorization logic in OnmsJexlUberspect that checked method calls on a whitelisted class object against the whitelisted class rather than against java.lang.Class itself, allowing reflection chains such as table.getClass().forName('java.lang.Runtime') to escape the sandbox. No public exploit or CISA KEV listing has been identified at time of analysis, but the upstream GitHub PR provides regression tests that precisely document the bypass technique.
Remote code execution in Sonatype Nexus Repository 3 (and legacy Nexus Repository 2) is achievable by any account holding the nexus:settings:update permission, which can submit arbitrary strings as realm identifiers to an internal configuration API that performs no validation against the registered realm set. Because unrecognized identifiers are persisted and re-evaluated on every realm load through a legacy code path (CWE-470, unsafe reflection), this allows unintended code to execute inside the Nexus Repository server process and can cause a persistent authentication lockout that is invisible through the administrative UI. A vendor-released patch is confirmed in Nexus Repository 3.95.0; no public exploit or CISA KEV listing has been identified at time of analysis.
Unsafe method invocation via Antlers template resolution in Statamic CMS enables unauthenticated remote attackers to destroy content and stored assets on affected installations. Sites running statamic/cms below 5.74.1 or in the 6.x line below 6.24.0 are vulnerable when their templates incorporate user-supplied input into Antlers template resolution - a deployment pattern present on developer-facing or dynamic sites. No public exploit or CISA KEV listing is identified at time of analysis; the CVSS AC:H rating reflects the required site-configuration precondition, tempering real-world exposure despite the destructive impact.
Unsafe class loading in the ORB (Object Request Broker) component of IBM WebSphere Application Server 8.5, 9.0, and Liberty Continuous Delivery allows a malicious or attacker-controlled IIOP server to force a WebSphere client/server to load and instantiate arbitrary Java classes over the network. Exploitation requires no authentication or user interaction (CVSS 9.8), and successful abuse can lead to loss of confidentiality, integrity, and availability, potentially culminating in remote code execution via dangerous class instantiation. There is no public exploit identified at time of analysis, and EPSS estimates only a 0.44% probability of exploitation in the next 30 days.
Arbitrary PHP function execution in ShopLentor (woolentor-addons) for WordPress up to and including version 3.3.7 allows authenticated administrators to invoke any PHP callable on the server via the woolentoropt/v1/custom-action REST API endpoint. The root cause is the plugin's handle_action() method passing the user-supplied 'callback' parameter directly into PHP's call_user_func() with no allowlist restriction, enabling full server-side code execution under the web server's privilege context. No public exploit code or CISA KEV listing has been identified at time of analysis; however, the admin-level requirement limits the realistic attacker pool to compromised or malicious site administrators.
Limited code execution risk in Apache OpenNLP through crafted model archives or untrusted format names permits arbitrary class instantiation without prior validation. The flaw exists in three code paths (GeneratorFactory, StreamFactoryRegistry, and StringInterners) that use Class.forName() on attacker-supplied data. Exploitation is contingent on the presence of a class with hazardous static initializers or no-arg constructors on the classpath; no active exploitation has been reported.
Remote code execution affects PaperCut MF and PaperCut NG through unsafe dynamic class loading in the database connection utilities, which instantiate JDBC driver classes from configurable driver names without validating them against an allowlist. An attacker who can control administrative system configuration parameters can force the server to load and execute arbitrary Java bytecode already present on the application classpath, running with the full privileges of the PaperCut server process. No public exploit identified at time of analysis, but the PR:H requirement and PaperCut's history of being targeted make prompt patching advisable.
Arbitrary PHP constructor execution is possible through the MailPreview feature of CakePHP debug_kit due to unsafe reflection (CWE-470), affecting all 4.x versions below 4.10.3 and 5.x versions below 5.2.4. An attacker with low-privileged network access to an application running in debug mode on a local or allowlisted hostname can pass a fully-qualified PHP class name as the previewName parameter, causing the controller to instantiate arbitrary classes. Vendor-released patches 4.10.3 and 5.2.4 address this issue; no public exploit has been identified at time of analysis.
Unsafe dynamic class instantiation in Vocos allows arbitrary code execution when a user loads a model from an attacker-controlled Hugging Face repository. The library's `Vocos.from_pretrained` fetches a remote `config.yaml` from a caller-supplied repository and passes it directly to `instantiate_class`, which imports and calls any Python callable named in the configuration without an allowlist. Any user who loads a Vocos model from a repository they do not fully trust is exposed to full code execution in their Python process. No public exploit has been identified at time of analysis, but the attack path requires minimal sophistication given the direct code path from remote config to `__import__`/`getattr`/call.
Unvalidated Class.forName() with initialization enabled in RabbitMQ Java Client's JSON-RPC tooling allows a network-positioned attacker to trigger arbitrary static initializers in the victim JVM. Applications using com.rabbitmq:amqp-client before 5.33.0 that employ the JsonRpcClient class are exposed when an attacker can control or spoof the system.describe broker response - either as a co-tenant on a shared broker or via network interception. Successful exploitation achieves code-like effects through static initializer execution and a secondary type-confusion path via mapper.parse, with full confidentiality, integrity, and availability impact on the client process. No public exploit identified at time of analysis, and this CVE is not listed in CISA KEV.
JEXL expression sandbox bypass in OpenNMS Meridian and Horizon allows a low-privileged authenticated user to load arbitrary Java classes on the server via the Measurements REST API, enabling confidentiality disclosure and integrity compromise. The flaw stems from incorrect authorization logic in OnmsJexlUberspect that checked method calls on a whitelisted class object against the whitelisted class rather than against java.lang.Class itself, allowing reflection chains such as table.getClass().forName('java.lang.Runtime') to escape the sandbox. No public exploit or CISA KEV listing has been identified at time of analysis, but the upstream GitHub PR provides regression tests that precisely document the bypass technique.
Remote code execution in Sonatype Nexus Repository 3 (and legacy Nexus Repository 2) is achievable by any account holding the nexus:settings:update permission, which can submit arbitrary strings as realm identifiers to an internal configuration API that performs no validation against the registered realm set. Because unrecognized identifiers are persisted and re-evaluated on every realm load through a legacy code path (CWE-470, unsafe reflection), this allows unintended code to execute inside the Nexus Repository server process and can cause a persistent authentication lockout that is invisible through the administrative UI. A vendor-released patch is confirmed in Nexus Repository 3.95.0; no public exploit or CISA KEV listing has been identified at time of analysis.
Unsafe method invocation via Antlers template resolution in Statamic CMS enables unauthenticated remote attackers to destroy content and stored assets on affected installations. Sites running statamic/cms below 5.74.1 or in the 6.x line below 6.24.0 are vulnerable when their templates incorporate user-supplied input into Antlers template resolution - a deployment pattern present on developer-facing or dynamic sites. No public exploit or CISA KEV listing is identified at time of analysis; the CVSS AC:H rating reflects the required site-configuration precondition, tempering real-world exposure despite the destructive impact.
Unsafe class loading in the ORB (Object Request Broker) component of IBM WebSphere Application Server 8.5, 9.0, and Liberty Continuous Delivery allows a malicious or attacker-controlled IIOP server to force a WebSphere client/server to load and instantiate arbitrary Java classes over the network. Exploitation requires no authentication or user interaction (CVSS 9.8), and successful abuse can lead to loss of confidentiality, integrity, and availability, potentially culminating in remote code execution via dangerous class instantiation. There is no public exploit identified at time of analysis, and EPSS estimates only a 0.44% probability of exploitation in the next 30 days.
Arbitrary PHP function execution in ShopLentor (woolentor-addons) for WordPress up to and including version 3.3.7 allows authenticated administrators to invoke any PHP callable on the server via the woolentoropt/v1/custom-action REST API endpoint. The root cause is the plugin's handle_action() method passing the user-supplied 'callback' parameter directly into PHP's call_user_func() with no allowlist restriction, enabling full server-side code execution under the web server's privilege context. No public exploit code or CISA KEV listing has been identified at time of analysis; however, the admin-level requirement limits the realistic attacker pool to compromised or malicious site administrators.
Limited code execution risk in Apache OpenNLP through crafted model archives or untrusted format names permits arbitrary class instantiation without prior validation. The flaw exists in three code paths (GeneratorFactory, StreamFactoryRegistry, and StringInterners) that use Class.forName() on attacker-supplied data. Exploitation is contingent on the presence of a class with hazardous static initializers or no-arg constructors on the classpath; no active exploitation has been reported.