CVE-2024-3123
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 · uneditedCHANGING Mobile One Time Password's uploading function in a hidden page does not filter file type properly. Remote attackers with administrator privilege can exploit this vulnerability to upload and run malicious file to execute system commands.
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 confidenceAn unrestricted file upload vulnerability exists in CHANGING Mobile One Time Password's uploading function on a hidden page. The function does not properly validate file types, allowing an authenticated administrator to upload malicious files that can be executed to run arbitrary system commands.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 CHANGING Mobile One Time Password installationSearch for files or directories containing 'changing' or 'motp' in the web root, or check installed software listings for this applicationAffected if The software is present on the system
-
Locate the hidden admin upload pageSearch for admin interfaces or hidden pages in the application that contain file upload functionality. Review web server access logs for requests to undocumented endpointsAffected if A hidden or undocumented upload page exists and is accessible
-
Verify authentication requirements for the upload functionAttempt to access the upload functionality or review access control configurations to determine if administrator authentication is enforcedAffected if The upload function is accessible to authenticated administrators without additional restrictions
-
Check file type validation on uploadsInspect the upload handler code or interceptor to see if file type validation is performed. Look for allowlist or blocklist validation logicAffected if No file type validation exists or validation can be bypassed
-
Determine upload directory location and web accessibilityReview the web server configuration and file system to find where uploaded files are stored. Check if the directory is within the web root and if script execution is permittedAffected if Uploaded files are stored inside the web root with executable permissions enabled
A user is affected if CHANGING Mobile One Time Password is installed, has an accessible hidden upload page for administrators, and stores uploaded files within the web root where they can be executed as scripts.
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 strict allowlist-based file type validation, store uploaded files outside the web root with randomized filenames, and disable script execution permissions on the upload directory to prevent uploaded files from being executed.
- 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-3123 — 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-3123 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