CVE-2024-11680
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedProjectSend 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceProjectSend versions before r1720 contain an improper authentication vulnerability in options.php that allows remote, unauthenticated attackers to send crafted HTTP requests and modify application configuration. This enables account creation, webshell uploads, and malicious JavaScript embedding.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< r1720CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed ProjectSend versionLocate the version identifier in your ProjectSend installation. Check files like version.php, CHANGELOG.txt, or the admin footer which often displays the version number. Also check git commit references if using git-based installation.Affected if The installed version is any build or commit reference earlier than r1720 (e.g., r1700, r1600, or any nightly build dated before the r1720 release).
-
Verify options.php exists and is web-accessibleConfirm that options.php exists in the web root of your ProjectSend installation. Use file system inspection or attempt a HEAD/GET request to yourdomain.com/options.php (do not submit any form data).Affected if The file exists and responds to HTTP requests without requiring authentication credentials.
-
Test options.php authentication requirementSend a crafted HTTP request to options.php with minimal or empty authentication headers. Observe whether the application returns a login prompt or allows the request to proceed to the processing logic.Affected if The endpoint accepts and processes requests without validating user session or authentication tokens.
-
Review for unauthorized administrative accountsLog into the admin panel and examine the Users section for any unfamiliar accounts with administrative privileges, especially those created recently or with suspicious usernames.Affected if Unexpected admin accounts exist that were not created by authorized administrators.
-
Inspect for webshell uploads or modified configurationExamine the /files/ or /uploads/ directories for unexpected PHP files with suspicious names. Check options.php and configuration files for injected JavaScript, eval() calls, or base64-encoded payloads.Affected if Unknown PHP files exist in upload directories, or configuration files contain suspicious code patterns indicating compromise.
You are affected if your installed ProjectSend version is earlier than r1720 AND the options.php endpoint is accessible without authentication, allowing unauthenticated configuration changes.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to ProjectSend r1720 or later. If immediate patching is not feasible, implement network-level restrictions to block unauthorized access to options.php.
r1720
- 1. Backup the existing ProjectSend installation including the database and configuration files.
- 2. Download the fixed version r1720 from the official ProjectSend repository (github.com/projectsend).
- 3. Replace the existing ProjectSend files with the new r1720 files, preserving the configuration and data directories.
- 4. Verify that the options.php file now requires authentication before allowing configuration changes.
- 5. Test that authenticated users can still access the administrative functions normally.
- 6. Review user accounts for any unauthorized accounts created by attackers.
- 7. Check for any malicious webshells or JavaScript that may have been uploaded during potential prior exploitation.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11680 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-11680 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data