dbcve.org
Shop Beat Media PlayerApplication · Shopbeat

CVE-2022-36244

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 →
58/100
Remediation priority · Elevated
Remotely reachable

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 suffers from Multiple Stored Cross-Site Scripting (XSS) vulnerabilities via Shop Beat Control Panel found at www.shopbeat.co.za 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

Multiple stored (persistent) Cross-Site Scripting vulnerabilities exist in the Shop Beat Media Player control panel interface (versions 2.5.95-3.2.57). Attackers can inject malicious JavaScript payloads into input fields within the control panel, which persist and execute when administrators or other users view the affected pages.

MitigationImplement comprehensive input validation and context-aware output encoding for all user-supplied data in the control panel. Additionally, deploy Content-Security-Policy (CSP) headers to mitigate script execution.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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. Identify Shop Beat Media Player version
    Access the control panel interface and locate the version information, typically found in the About page, footer, or system settings. Alternatively, check the application's main entry point or help/documentation section.
    Affected if The installed version falls within the range >= 2.5.95 and < 3.2.57.
  2. Confirm control panel access
    Verify that the Shop Beat Media Player control panel interface is accessible and operational. Attempt to log in or access the administrative dashboard.
    Affected if The control panel interface is accessible and running.
  3. Identify exploitable input fields
    Navigate through the control panel and locate input fields where user data is stored and displayed back, such as media metadata fields, configuration settings, or user profile inputs.
    Affected if Input fields that store and display user-supplied data without sanitization are present in the control panel.
  4. Check for injected JavaScript payloads
    Inspect the HTML source of control panel pages or review stored configuration/data files for suspicious script tags, event handlers, or encoded JavaScript payloads.
    Affected if Unexpected script tags, javascript: URIs, or event handler attributes are found in stored data or rendered HTML.
  5. Review application logs for XSS indicators
    Examine server or application logs for patterns indicating XSS attempts, such as requests containing <script>, onerror, onload, or similar JavaScript event handlers in input parameters.
    Affected if Log entries contain suspicious JavaScript payloads or XSS attack patterns in request parameters.

A user is affected if the installed Shop Beat Media Player version is between 2.5.95 and 3.2.57 and the control panel interface with persistent input fields is accessible and processing user-supplied data.

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 comprehensive input validation and context-aware output encoding for all user-supplied data in the control panel. Additionally, deploy Content-Security-Policy (CSP) headers to mitigate script execution.

Recommended fix Moderate confidence

Shop Beat Media Player version 3.2.57 or later

  1. Identify the current version of Shop Beat Media Player installed on the system
  2. Create a complete backup of the current installation including database and configuration files
  3. Access the Shop Beat update mechanism or download the updated version from www.shopbeat.co.za
  4. Upgrade Shop Beat Media Player to version 3.2.57 or later
  5. Verify the upgrade was successful by checking the installed version
  6. Test the control panel functionality to ensure the application is working correctly after the upgrade
  7. Confirm that the XSS vulnerabilities are no longer present by reviewing the control panel inputs

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
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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