Summary
Orchid Platform has Method Exposure Vulnerability in Modals
Workarounds
If upgrading to version 14.43.0 is not immediately possible, you can mitigate the vulnerability by implementing middleware to intercept and validate requests to asynchronous modal endpoints, allowing only approved methods and parameters.
Example middleware:
namespace App\Http\Middleware;
use Closure;
use Illuminate\Http\Request;
use Symfony\Component\HttpFoundation\Response;
class PreventBruteForceOnAsyncRoute
{
/**
* Methods that are restricted from being invoked via the async route.
*/
protected array $restrictedMethods = [
'validate',
'handle',
'__invoke',
'validateWith',
'validateWithBag',
'callAction',
];
/**
* Handle an incoming request.
*/
public function handle(Request $request, Closure $next): Response
{
// Retrieve the current route from the request.
/** @var \Illuminate\Routing\Route|null $route */
$route = $request->route();
// Allow requests to routes other than "platform.async".
if ($route?->getName() !== 'platform.async') {
return $next($request);
}
// Block requests attempting to invoke any of the restricted methods.
if (in_array($route->parameter('method'), $this->restrictedMethods)) {
abort(503, sprintf(
'Access to the "%s" method is restricted.',
$route->parameter('method')
));
}
// Continue request processing for other cases.
return $next($request);
}
}
References
Acknowledgements
We would like to extend our sincere gratitude to Positive Technologies and researcher Vladislav Gladky for identifying the vulnerability and their significant contribution to enhancing the security of our platform. Their expertise and dedication play a crucial role in making Orchid more reliable and secure for all users.
Impact
This vulnerability is a method exposure issue (CWE-749: Exposed Dangerous Method or Function) in the Orchid Platform’s asynchronous modal functionality, affecting users of Orchid Platform version 8 through 14.42.x. Attackers could exploit this vulnerability to call arbitrary methods within the Screen class, leading to potential brute force of database tables, validation checks against user credentials, and disclosure of the server’s real IP address.
CVE-2024-51992 has a CVSS score of 4.1 (Medium). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (14.43.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The issue has been patched in the latest release, version 14.43.0, released on November 6, 2024. Users should upgrade to version 14.43.0 or later to address this vulnerability.
Frequently Asked Questions
- What is CVE-2024-51992? CVE-2024-51992 is a medium-severity security vulnerability in orchid/platform (composer), affecting versions >= 8.0, < 14.43.0. It is fixed in 14.43.0.
- How severe is CVE-2024-51992? CVE-2024-51992 has a CVSS score of 4.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of orchid/platform are affected by CVE-2024-51992? orchid/platform (composer) versions >= 8.0, < 14.43.0 is affected.
- Is there a fix for CVE-2024-51992? Yes. CVE-2024-51992 is fixed in 14.43.0. Upgrade to this version or later.
- Is CVE-2024-51992 exploitable, and should I be worried? Whether CVE-2024-51992 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2024-51992 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2024-51992? Upgrade
orchid/platformto 14.43.0 or later.