CVE-2024-49674
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in lukashuser EKC Tournament Manager ekc-tournament-manager allows Upload a Web Shell to a Web Server.This issue affects EKC Tournament Manager: from n/a through <= 2.2.1.
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 · moderate confidenceCSRF vulnerability in EKC Tournament Manager enables attackers to trick authenticated users into uploading a web shell to the server, achieving remote code execution. The attack exploits the lack of anti-CSRF tokens on file upload endpoints, allowing malicious requests to be submitted when a logged-in user visits a malicious site or clicks a crafted link.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 EKC Tournament Manager versionLocate the application files and check for version information in configuration files, about pages, or metadata (e.g., version.php, info.json, or admin dashboard 'About' section). Compare the installed version against any known version ranges.Affected if The installed version matches the vulnerable release of EKC Tournament Manager.
-
Confirm file upload functionality is enabledNavigate to the application's admin or user panel and locate any file upload features (e.g., tournament image upload, document attachment, profile picture upload). Check if the upload endpoint is accessible and functional.Affected if File upload functionality exists and is accessible to authenticated users.
-
Inspect upload endpoint for anti-CSRF protectionCapture a request to the file upload endpoint using browser developer tools or a proxy. Examine the HTML form or AJAX request for the presence of a CSRF token parameter (commonly named 'csrf_token', 'token', '_token', or 'anticsrf'). Also check if the request includes a custom header typically used for CSRF validation.Affected if The file upload request does not include a CSRF token parameter or custom anti-CSRF header.
-
Verify Origin/Referer header validationSend a file upload request with a mismatched or missing Origin/Referer header (e.g., using curl with modified headers). Observe whether the server rejects the request or processes it regardless.Affected if The server accepts file upload requests with arbitrary or missing Origin/Referer headers.
A user is affected if they run a vulnerable version of EKC Tournament Manager with accessible file upload functionality that lacks anti-CSRF token protection on its endpoints.
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.
From vendor dataImplement synchronizer token pattern (anti-CSRF tokens) on all state-changing operations, especially file upload functionality, and validate Origin/Referer headers as secondary defense. Additionally, enforce strict Content-Type validation and file extension allow-listing on upload endpoints.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49674 — 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-49674 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