dbcve.org
Shop Beat Media PlayerApplication · Shopbeat

CVE-2022-36243

MEDIUM · 5.3 CVSS v3.1 Published 2023-05-30
Fix available
A fix is available. Upgrade to 3.2.57 or later.
See remediation →
62/100
Remediation priority · Elevated
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 Directory Traversal via server.shopbeat.co.za. Information Exposure Through Directory Listing vulnerability in "studio" software of Shop Beat. This issue affects: Shop Beat studio studio versions prior to 3.2.57 on arm.

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 studio versions prior to 3.2.57 contain a directory traversal vulnerability via server.shopbeat.co.za that allows unauthenticated attackers to access files and directories outside the web root through the 'studio' software, resulting in information disclosure.

MitigationUpgrade to Shop Beat studio version 3.2.57 or later. Additionally, disable directory listing on the web server and implement proper access controls to prevent traversal attacks.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Identify installed Shop Beat Media Player studio version
    Check the software version reported in the studio application or About section, typically accessible through the studio interface or installed program metadata
    Affected if Installed version is 2.5.95 or higher but lower than 3.2.57
  2. Confirm studio web component is accessible
    Attempt to access the studio web interface via the server endpoint (typically at server.shopbeat.co.za or the configured studio server URL)
    Affected if The studio web component is exposed and reachable over the network
  3. Verify directory listing is enabled on the web server
    Check the web server configuration (such as Apache, Nginx, or IIS) for directory listing options - look for 'Options +Indexes' in Apache or 'autoindex on' in Nginx
    Affected if Directory listing is enabled on the web server hosting the studio component
  4. Test for directory traversal vulnerability
    Send a crafted HTTP request to the studio endpoint using path traversal sequences such as '../' or '..\' to access files outside the web root, for example: GET /../../../../etc/passwd
    Affected if The server returns file contents from outside the intended web root directory, indicating the traversal vulnerability is present

You are affected if the installed Shop Beat Media Player studio version is between 2.5.95 and 3.2.57 (exclusive) AND the studio web component is exposed, allowing unauthorized directory traversal access to files outside the web root.

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

Upgrade to Shop Beat studio version 3.2.57 or later. Additionally, disable directory listing on the web server and implement proper access controls to prevent traversal attacks.

Recommended fix High confidence

Shop Beat Media Player 3.2.57 or later

  1. 1. Backup the current Shop Beat Media Player installation and all relevant data/configuration files.
  2. 2. Navigate to the official Shop Beat download page at www.shopbeat.co.za
  3. 3. Download Shop Beat Media Player version 3.2.57 or later
  4. 4. Uninstall the current vulnerable version (2.5.95 through 3.2.56)
  5. 5. Install the patched version 3.2.57 or newer
  6. 6. Restore any backed-up configuration and data
  7. 7. Verify the fix by confirming that directory traversal via server.shopbeat.co.za is no longer possible and the 'studio' directory listing no longer exposes sensitive information

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

Fix this in Shop Beat Media Player Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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