Skip to content
Server Security Center
KEVcritical9.8

CVE-2024-11680: ProjectSend Improper Authentication

ProjectSend · listed in the CISA catalog of actively exploited vulnerabilities since 2024-12-03.

CVSS v3.1 (CVE record)
9.8
critical
EPSS (exploit probability, 30 days)
92%
higher than 99.8% of all CVEs
Added to CISA KEV
2024-12-03
US federal due date 2024-12-24
Automatable (CISA SSVC)
yes
technical impact: total

CVE-2024-11680 explained

CVE-2024-11680 is an improper authentication vulnerability in ProjectSend, a server software product, affecting versions prior to r1720. Remote, unauthenticated attackers can change the application's configuration through crafted HTTP requests to options.php. CISA lists it as known to be exploited, so unpatched internet-facing installations face serious risk.

Impact

An attacker needs only network access to the application. No credentials or user interaction are required. By modifying the configuration, the attacker can create accounts, upload webshells and embed malicious JavaScript. This can lead to high loss of confidentiality, integrity and availability. CISA rates the flaw as automatable, meaning exploitation can be done at scale, with total technical impact. Attackers are known to exploit it in the wild.

Who is affected

The CVE record lists ProjectSend versions before r1720 (< r1720) as affected. The fix is included in r1720. Any ProjectSend installation running a release earlier than r1720 should be treated as vulnerable.

Written with AI from the data on this page and checked against it automatically.

Official description

ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Remote, unauthenticated attackers can exploit this flaw by sending crafted HTTP requests to options.php, enabling unauthorized modification of the application's configuration.

Successful exploitation allows attackers to create accounts, upload webshells, and embed malicious JavaScript.

CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • ProjectSend
    Affected
    • < r1720
    Fixed in
    • r1720

How to fix it

What to do

  1. Upgrade all ProjectSend installations to r1720 or later.
  2. Follow the vendor advisory and apply any mitigations it describes; CISA requires discontinuing use if mitigations are unavailable.
  3. Restrict network access to ProjectSend, avoiding direct internet exposure where possible.
  4. Review the application configuration and user accounts for unauthorized changes or newly created accounts.
  5. Check the server for unexpected uploaded files such as webshells and for injected JavaScript.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-306 Missing Authentication for Critical Function

Questions about CVE-2024-11680

Is CVE-2024-11680 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2024-12-03, with a US federal due date of 2024-12-24. Whether it is used in ransomware campaigns is listed as unknown.
Which version fixes the vulnerability?
The CVE record names r1720 as the fixed version. All ProjectSend versions before r1720 are affected.
Do attackers need an account to exploit it?
No. The flaw can be exploited remotely by unauthenticated attackers without user interaction, which is why limiting exposure and patching quickly matter.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.