CVE-2024-46054
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 · uneditedOpenVidReview 1.0 is vulnerable to Incorrect Access Control. The /upload route is accessible without authentication, allowing any user to upload files.
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 confidenceOpenVidReview 1.0 contains an Incorrect Access Control vulnerability where the /upload endpoint is accessible without any authentication. This allows any unauthenticated user to upload files to the server, which could lead to remote code execution if malicious files (e.g., web shells) are uploaded.
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= 1.0CVSS 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.
-
Confirm OpenVidReview installation and versionIdentify if the OpenVidReview application is deployed in your environment. Check the application's version information (typically found in the application metadata, about page, or version file). Compare your installed version to the affected version: Davidguva Openvidreview = 1.0Affected if The installed version is OpenVidReview 1.0
-
Identify the /upload endpointReview the application's routing configuration or source code to locate the /upload endpoint. This endpoint handles file upload functionality in the application.Affected if The /upload endpoint exists and is defined in the application routes
-
Verify authentication requirement on /uploadTest accessing the /upload endpoint using an unauthenticated request (e.g., using curl or a browser without logging in). Check the endpoint's code or configuration to determine if any authentication check is performed before processing upload requests.Affected if The /upload endpoint processes requests without requiring authentication credentials
-
Confirm file upload functionality is enabledAttempt to send a valid file upload request to the /upload endpoint without authentication. Observe whether the application accepts and processes the uploaded file without enforcing access controls.Affected if Files can be uploaded to the /upload endpoint by unauthenticated users
You are affected if OpenVidReview 1.0 is installed and the /upload endpoint accepts unauthenticated requests to upload files.
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 authentication enforcement on the /upload route and add proper file type validation to restrict uploads to only allowed file types.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46054 — 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-46054 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