CVE-2022-25275

In some situations, the Image module does not correctly check access to image files not stored in the standard public files directory when generating derivative images using the image styles system.

Access to a non-public file is checked only if it is stored in the "private" file system. However, some contributed modules provide additional file systems, or schemes, which may lead to this vulnerability.

This vulnerability is mitigated by the fact that it only applies when the site sets (Drupal 9) $config['image.settings']['allow_insecure_derivatives'] or (Drupal 7) $conf['image_allow_insecure_derivatives'] to TRUE. The recommended and default setting is FALSE, and Drupal core does not provide a way to change that in the admin UI.

Some sites may require configuration changes following this security release. Review the release notes for your Drupal version if you have issues accessing files or image styles after updating.

CVE-2022-25275 has a CVSS score of 7.5 (High). The vector is network-reachable, no 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 (7.91, 9.3.19, 9.4.3); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2022-25275? CVE-2022-25275 is a high-severity security vulnerability in drupal/core (composer), affecting versions >= 7.0.0, < 7.91. It is fixed in 7.91, 9.3.19, 9.4.3.
2. How severe is CVE-2022-25275? CVE-2022-25275 has a CVSS score of 7.5 (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-25275? drupal/core (composer) versions >= 7.0.0, < 7.91 is affected.
4. Is there a fix for CVE-2022-25275? Yes. CVE-2022-25275 is fixed in 7.91, 9.3.19, 9.4.3. Upgrade to this version or later.
5. Is CVE-2022-25275 exploitable, and should I be worried? Whether CVE-2022-25275 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-25275 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-25275?
   • Upgrade drupal/core to 7.91 or later
   • Upgrade drupal/core to 9.3.19 or later
   • Upgrade drupal/core to 9.4.3 or later