dbcve.org
Shop Beat Media PlayerApplication · Shopbeat

CVE-2022-36249

MEDIUM · 5.4 CVSS v3.1 Published 2023-05-30
Fix available
A fix is available. Upgrade to 3.2.57 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
Shop Beat Solutions (Pty) LTD Shop Beat Media Player 2.5.95 up to 3.2.57 is vulnerable to Bypass 2FA via APIs. For Controlpanel Lite. "After login we are directly able to use the bearer token or jsession ID to access the apis instead of entering the 2FA code. Thus, leading to bypass of 2FA on API level.

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 confidence

Shop Beat Media Player's Controlpanel Lite API fails to enforce two-factor authentication validation. After initial login, the bearer token or jsession ID can be used to directly access APIs without entering the 2FA code, allowing complete bypass of the two-factor authentication mechanism at the API level.

MitigationImplement proper 2FA validation checks on all API endpoints to ensure the 2FA code is verified before granting access, regardless of whether a valid bearer token or jsession ID is present in the request.

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
Shop Beat Media PlayerApplication
Affected:>= 2.5.95, < 3.2.57

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

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Confirm Shop Beat Media Player is installed
    Locate the Shop Beat Media Player installation on your system. Check for the application directory or installed software listing that contains 'Shop Beat' or 'Shopbeat' in the name.
    Affected if The software is present on the system
  2. Identify the installed version
    Access the application version information through the software's about page, installation directory metadata, or system registry entry for Shop Beat Media Player. Compare the version number against the affected range of >= 2.5.95 and < 3.2.57.
    Affected if The installed version falls within >= 2.5.95 and < 3.2.57
  3. Verify two-factor authentication is enabled
    Check the application configuration or security settings within Shop Beat Media Player to confirm whether 2FA has been enabled as a login requirement.
    Affected if 2FA is enabled in the application settings
  4. Test API access without 2FA code
    Using valid authentication credentials (bearer token or jsession ID obtained from initial login), attempt to access API endpoints directly without providing a 2FA code. Compare behavior against expected 2FA enforcement.
    Affected if API requests succeed with valid session credentials alone, bypassing 2FA code requirement

You are affected if Shop Beat Media Player version is between 2.5.95 and 3.2.57 (inclusive of 2.5.95, exclusive of 3.2.57) and 2FA can be bypassed using only bearer token or jsession ID without providing a valid 2FA code.

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.

dbcve · scoped
Upgrade available Upgrade to 3.2.57 or later
Fixed in 3.2.57
Interim mitigation

Implement proper 2FA validation checks on all API endpoints to ensure the 2FA code is verified before granting access, regardless of whether a valid bearer token or jsession ID is present in the request.

Recommended fix High confidence

Shop Beat Media Player 3.2.57 or later

  1. Identify all deployments of Shop Beat Media Player in the environment
  2. Check the current version of each Shop Beat Media Player installation
  3. For instances with versions >= 2.5.95 and < 3.2.57, plan and schedule an upgrade
  4. Backup all configuration and data before upgrading
  5. Upgrade Shop Beat Media Player to version 3.2.57 or later following vendor documentation
  6. After upgrade, verify that 2FA is properly enforced on API endpoints
  7. Confirm that API access now correctly requires valid 2FA code in addition to bearer token or jsession ID

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Shop Beat Media Player Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-36249 — 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-2022-36249 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