dbcve.org
StudyplusApplication · Wantedlyinc

CVE-2020-5667

MEDIUM · 5.5 CVSS v3.1 Published 2020-11-06
Fix available
A fix is available. Upgrade to after 8.29.0 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
Studyplus App for Android v6.3.7 and earlier and Studyplus App for iOS v8.29.0 and earlier use a hard-coded API key for an external service. By exploiting this vulnerability, API key for an external service may be obtained by analyzing data in the app.

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 confidence

The Studyplus mobile applications for Android (v6.3.7 and earlier) and iOS (v8.29.0 and earlier) contain a hard-coded API key embedded within the app's data or code. An attacker with access to the app binary or its data files can extract this API key through static analysis or by inspecting network traffic, potentially gaining unauthorized access to the associated external service.

MitigationReplace the hardcoded API key with a proper authentication mechanism (e.g., OAuth, token-based auth), rotate any compromised API keys, and release updated app versions to both the Android and iOS app stores.

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
StudyplusApplication
Affected:<= 6.3.7<= 8.29.0

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Android app version
    Open Google Play Store, search for Studyplus, or go to Settings > Apps > Studyplus to view the installed version number
    Affected if Version number is 6.3.7 or lower
  2. Check installed iOS app version
    Open the App Store, search for Studyplus, tap on the app, and view the version information under the app description
    Affected if Version number is 8.29.0 or lower
  3. Verify hardcoded API key presence (optional)
    Extract the app APK (Android) or IPA (iOS) file, then use a hex editor, strings command, or APK analysis tool (like jadx) to search for API keys or suspicious hardcoded strings within the app binary
    Affected if A hardcoded API key or authentication token is found embedded in the app code or resources

If the installed Studyplus app version is 6.3.7 or lower on Android, or 8.29.0 or lower on iOS, the hardcoded API key vulnerability is present in the environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 8.29.0
Interim mitigation

Replace the hardcoded API key with a proper authentication mechanism (e.g., OAuth, token-based auth), rotate any compromised API keys, and release updated app versions to both the Android and iOS app stores.

Fix this in Studyplus Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-5667 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-5667 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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