Cyber Resilience

CVE-2024-2449

CSRF in Progress Loadmaster 7.2.49.0 – 7.2.54.9

Published
22 March 2024
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.13 96th percentile
Risk Priority 65 floored blend · peak EPSS

Summary

CVE-2024-2449 is a high-severity CSRF (CWE-352) vulnerability in Progress Loadmaster. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 4% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SC-23 (Session Authenticity) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

A cross-site request forgery vulnerability tracked as CVE-2024-2449 affects LoadMaster, the load-balancing and application-delivery appliance from Progress Software (formerly Kemp Technologies). The flaw, assigned CWE-352, allows an attacker to craft a malicious third-party site that, when visited by an authenticated LoadMaster administrator, causes the administrator’s browser to issue unauthorized HTTP requests to the appliance.

An attacker who already knows the IP address or hostname of a target LoadMaster instance can exploit the issue by luring an authenticated administrator to the attacker-controlled page. Successful exploitation enables the attacker to perform arbitrary administrative actions on the LoadMaster appliance on behalf of the victim, with the CVSS 7.5 score reflecting high impact on confidentiality, integrity, and availability under the condition that the victim interacts with the malicious site.

Public advisories published by Progress and Kemp Technologies reference both CVE-2024-2449 and the related CVE-2024-2448; the EPSS score rose from a low baseline to a peak of 0.0640 on 2025-12-11 before receding to its current value of 0.0332, indicating a measurable increase in observed exploitation interest after disclosure.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A cross-site request forgery vulnerability has been identified in LoadMaster. It is possible for a malicious actor, who has prior knowledge of the IP or hostname of a specific LoadMaster, to direct an authenticated LoadMaster administrator to a third-party site.…

more

In such a scenario, the CSRF payload hosted on the malicious site would execute HTTP transactions on behalf of the LoadMaster administrator.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-40048Same vendor: Progress
CVE-2024-8489Shared CWE-352
CVE-2024-51638Shared CWE-352
CVE-2025-23804Shared CWE-352
CVE-2024-36667Shared CWE-352
CVE-2024-26445Shared CWE-352
CVE-2024-22601Shared CWE-352
CVE-2023-50766Shared CWE-352
CVE-2025-9635Shared CWE-352
CVE-2025-30541Shared CWE-352

Affected Assets

progress
loadmaster
7.1.35.10, 7.2.48.10 · 7.2.49.0 — 7.2.54.9 · 7.2.55.0 — 7.2.59.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V3.3.2
  • V3.5.1
  • V10.2.1

Mitigating Controls (NIST 800-53 r5) AI

Access enforcement requires verifying that state-changing requests originate from the authenticated user rather than a forged cross-site source.

Protecting session authenticity prevents attackers from replaying or forging authenticated requests via the victim's browser.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require anti-CSRF controls such as tokens or SameSite attributes.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

mitigates

By denying access to phishing or malicious sites, the control lowers the likelihood that a user will be tricked into submitting a forged request that performs an unintended action on another site.

none

Contextual intelligence about emerging CSRF toolkits can be translated into updated anti-CSRF token or same-site policy configurations across applications.

References