CVE-2022-25277

Drupal core sanitizes filenames with dangerous extensions upon upload and strips leading and trailing dots from filenames to prevent uploading server configuration files.

However, the protections for these two vulnerabilities previously did not work correctly together. As a result, if the site were configured to allow the upload of files with an htaccess extension, these files' filenames would not be properly sanitized. This could allow bypassing the protections provided by Drupal core's default .htaccess files and possible remote code execution on Apache web servers.

This issue is mitigated by the fact that it requires a field administrator to explicitly configure a file field to allow htaccess as an extension (a restricted permission), or a contributed module or custom code that overrides allowed file uploads.

The application accepts file uploads without adequately restricting the file type or content. Typical impact: remote code execution if the uploaded file can be served and executed on the server.

CVE-2022-25277 has a CVSS score of 7.2 (High). 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 (9.3.19, 9.4.3); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2022-25277? CVE-2022-25277 is a high-severity unrestricted upload of dangerous file types vulnerability in drupal/core (composer), affecting versions >= 8.0.0, < 9.3.19. It is fixed in 9.3.19, 9.4.3. The application accepts file uploads without adequately restricting the file type or content.
2. How severe is CVE-2022-25277? CVE-2022-25277 has a CVSS score of 7.2 (High). 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.
3. Which versions of drupal/core are affected by CVE-2022-25277? drupal/core (composer) versions >= 8.0.0, < 9.3.19 is affected.
4. Is there a fix for CVE-2022-25277? Yes. CVE-2022-25277 is fixed in 9.3.19, 9.4.3. Upgrade to this version or later.
5. Is CVE-2022-25277 exploitable, and should I be worried? Whether CVE-2022-25277 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
6. What actually determines whether CVE-2022-25277 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.
7. How do I fix CVE-2022-25277?
   • Upgrade drupal/core to 9.3.19 or later
   • Upgrade drupal/core to 9.4.3 or later