Threats / ProjectSend / CVE-2024-11680
CVE-2024-11680
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
ProjectSend vulnerability
ProjectSend contains an improper authentication vulnerability in options.php that allows unauthenticated attackers to modify application configuration, create accounts, upload webshells, and inject malicious JavaScript.
Verdict
Today item — known-exploited.
Remote unauthenticated attackers can bypass authentication controls to gain administrative access, enabling account creation, arbitrary file upload, and client-side code injection attacks against application users.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
6 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-12-03).
Probability (EPSS)
EPSS 0.91559 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: ProjectSend, ProjectSend. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-287 Improper Authentication — weakness family: Authentication.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I send crafted HTTP requests to options.php without credentials to bypass authentication checks.
Business
Authentication controls fail to protect sensitive configuration endpoints, creating an open door for unauthorized access.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I modify application configuration settings to create new administrative accounts under my control.
Business
Attackers gain persistent administrative access to the application, bypassing all user access controls.
3
Lateral reach — past segmentation narrative 3
Attacker
I upload webshell files to the server through the compromised application interface.
Business
The server is compromised with persistent remote code execution capability, enabling data theft and lateral movement.
4
Data at risk — exfiltration narrative 4
Attacker
I inject malicious JavaScript into application pages served to legitimate users.
Business
Client devices are compromised through malware distribution, credential theft, or further attack propagation to users' networks.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05