CVE-2026-18424 Vulnerability Analysis & Exploit Details

CVE-2026-18424
Vulnerability Scoring

7.1
/10
Very High Risk

Highly exploitable, CVE-2026-18424 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Changed
    Successful exploitation can impact components beyond the vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-18424 Details

Status: Analyzed

Last updated: 🕠 21 Sep 2026, 17:50 UTC
Originally published on: 🕗 15 Sep 2026, 20:17 UTC

Time between publication and last update: 5 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N

CVE-2026-18424 Vulnerability Summary

CVE-2026-18424: Concrete CMS 9.0.0 to 9.5.2 is vulnerable to Server-Side Request Forgery iremote file import via cross-port reuse of a host's validated DNS pin. When multiple remote URLs share the same host, only the first `ValidatedRemoteUrl` is retained and reused for every later URL with that host. A low-privileged authenticated user permitted to import files could therefore supply a DNS-rebinding host that resolved to a public address during validation and to a private or loopback address during the unpinned download, causing the server to fetch internal-only resources such as loopback services, internal admin panels, or cloud metadata endpoints and to save the responses into the file manager. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 2.1 with vector CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N. Thanks Ahmad Wicaksono (sonix03) for reporting.

Assessing the Risk of CVE-2026-18424

Access Complexity Graph

The exploitability of CVE-2026-18424 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-18424

This vulnerability, CVE-2026-18424, requires a high level of attack complexity and low privileges, making it difficult but not impossible to exploit. Organizations should ensure robust security configurations to mitigate risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-18424, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-18424, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2026-18424 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: Low
    Exploiting CVE-2026-18424 may cause minor changes to data without severely impacting its accuracy.
  • Availability: None
    CVE-2026-18424 does not impact system availability.

CVE-2026-18424 References

External References

CWE Common Weakness Enumeration

CWE-918

CAPEC Common Attack Pattern Enumeration and Classification

  • Server Side Request Forgery CAPEC-664 An adversary exploits improper input validation by submitting maliciously crafted input to a target application running on a server, with the goal of forcing the server to make a request either to itself, to web services running in the server’s internal network, or to external third parties. If successful, the adversary’s request will be made with the server’s privilege level, bypassing its authentication controls. This ultimately allows the adversary to access sensitive data, execute commands on the server’s network, and make external requests with the stolen identity of the server. Server Side Request Forgery attacks differ from Cross Site Request Forgery attacks in that they target the server itself, whereas CSRF attacks exploit an insecure user authentication mechanism to perform unauthorized actions on the user's behalf.

Vulnerable Configurations

  • cpe:2.3:a:concretecms:concrete_cms:9.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.1.3:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.1.3:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.2.0:-:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.2.0:-:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.2.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.2.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.2.5:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.2.6:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.2.6:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.2.7:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.2.7:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.2.8:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.2.8:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.2.9:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.2.9:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.3.3:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.3.3:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.3.4:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.3.4:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.3.5:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.3.5:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.3.6:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.3.6:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.3.7:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.3.7:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.3.8:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.3.8:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.3.9:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.3.9:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.4.0:-:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.4.0:-:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.4.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.4.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.4.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.4.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.4.3:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.4.3:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.4.4:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.4.4:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.4.5:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.4.5:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.4.6:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.4.6:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.4.7:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.4.7:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.4.8:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.4.8:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.5.0:-:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.5.0:-:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.5.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.5.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.5.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.5.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.5.2:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.5.2:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-18424: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-95512 – A flaw was found in FreeType, specifically within its CID font loader. A remote attacker could exploit this vulnerability by tricking a user into o...
  • CVE-2026-91784 – cjbassi/gotop is vulnerable to local argument injection via process termination functionality. The process name is passed directly to pkill without...
  • CVE-2026-80464 – Server-Side request forgery (SSRF) vulnerability in HAVELSAN Inc. Sef - AI Chatbot Platform allows Server Side Request Forgery. This issue affects...
  • CVE-2026-80443 – Improper certificate validation vulnerability in HAVELSAN Inc. Sef - AI Chatbot Platform allows Adversary in the Middle (AiTM). This issue affects...
  • CVE-2026-80337 – Missing Authorization vulnerability in HAVELSAN Inc. Sef - AI Chatbot Platform allows Accessing Functionality Not Properly Constrained by ACLs. Th...