CVE-2021-28174
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 · uneditedMitake smart stock selection system contains a broken authentication vulnerability. By manipulating the parameters in the URL, remote attackers can gain the privileged permissions to access transaction record, and fraudulent trading without login.
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 confidenceBroken authentication vulnerability in Mitake smart stock selection system allows unauthenticated remote attackers to manipulate URL parameters to bypass login and gain privileged access, enabling unauthorized access to transaction records and fraudulent trading.
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<= 2020-06-23CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
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 Mitake Smart Stock Selection installationSearch the system for Mitake Smart Stock Selection software - check installed programs list, application directories, or search for executable filenames containing 'mitake' or 'smartstock'Affected if The software is present on the system
-
Determine installed version and build dateLocate the application version information - typically in the application's about dialog, installation directory readme/version file, or Windows registry uninstall entry. Look for build date or version numberAffected if Version is dated 2020-06-23 or earlier, or version number is at or below the last vulnerable release
-
Check if web interface is exposedIdentify if the application's web interface or API endpoints are accessible externally - review firewall rules, reverse proxy configurations, and network exposure settings for ports used by the applicationAffected if The web interface is accessible from untrusted networks without VPN or proper network segmentation
-
Review authentication configurationExamine the application's configuration files or admin panel for authentication settings - check if session management uses predictable parameters, if URL-based authentication bypass mechanisms exist, or if privileged endpoints lack proper authorization checksAffected if Authentication relies solely on client-supplied URL parameters without server-side validation, or session tokens are easily predictable
-
Analyze access logs for anomalous requestsReview web server or application access logs for patterns indicating parameter manipulation - look for requests to privileged endpoints with manipulated session, user, or role parameters in URLsAffected if Logs show successful unauthorized access attempts or requests with modified authentication parameters reaching privileged functions
A user is affected if Mitake Smart Stock Selection version 2020-06-23 or earlier is installed and its web interface is network-accessible, allowing URL parameter manipulation to bypass authentication.
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 robust authentication mechanisms with proper session management, enforce rigorous authorization checks on all privileged operations, and validate/sanitize all user-controllable parameters to prevent manipulation.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-28174 — 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-2021-28174 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