dbcve.org
Shop Beat Media PlayerApplication · Shopbeat

CVE-2022-36247

CRITICAL · 9.1 CVSS v3.1 Published 2023-05-30
Fix available
A fix is available. Upgrade to 3.2.57 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 IDOR via controlpanel.shopbeat.co.za.

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

IDOR vulnerability in Shop Beat Media Player's control panel allows authenticated users to access or modify sensitive data belonging to other users by manipulating object references (such as IDs in requests), without proper authorization validation.

MitigationImplement proper object-level authorization checks on all endpoints in the control panel, ensuring users can only access resources they own or are explicitly permitted to access.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Identify Shop Beat Media Player installation
    Locate the Shop Beat Media Player application on your system. Check for installation directories, services, or web applications running on your server.
    Affected if Shop Beat Media Player is installed and running.
  2. Determine installed version
    Access the application's version information through the control panel, about page, or by checking application files/config for the version number.
    Affected if The installed version is >= 2.5.95 AND < 3.2.57.
  3. Verify control panel is accessible
    Confirm the Shop Beat Media Player control panel web interface is reachable. Attempt to access the control panel URL or check network bindings.
    Affected if The control panel is exposed and accessible over the network.
  4. Confirm authentication is enabled
    Check that user authentication is required to access the control panel and that user accounts can be created or exist in the system.
    Affected if The control panel allows authenticated user accounts to log in.
  5. Review object reference handling in requests
    Log into the control panel with a test user account. Examine requests to the control panel for object references (such as IDs, record numbers, or resource identifiers) that could be manipulated to access other users' data.
    Affected if The application uses predictable object references in requests without proper ownership validation.

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 the control panel with authenticated user accounts is accessible.

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 object-level authorization checks on all endpoints in the control panel, ensuring users can only access resources they own or are explicitly permitted to access.

Recommended fix Moderate confidence

3.2.57 or later

  1. 1. Identify the current version of Shop Beat Media Player installed in your environment
  2. 2. If the current version is between 2.5.95 and 3.2.56 (inclusive), plan for an upgrade
  3. 3. Before upgrading, perform a full backup of the current installation including configuration files and data
  4. 4. Download Shop Beat Media Player version 3.2.57 or the latest available version from the official vendor (www.shopbeat.co.za)
  5. 5. Test the upgrade in a non-production environment first to verify compatibility
  6. 6. Apply the upgrade to production systems following vendor documentation
  7. 7. Verify that the IDOR vulnerability via controlpanel.shopbeat.co.za is no longer exploitable after the upgrade
  8. 8. Confirm the upgraded version is 3.2.57 or later

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

Fix this in Shop Beat Media Player Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

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