dbcve.org
Audio MerchantWordPress extension · Myaudiomerchant

CVE-2023-6197

MEDIUM · 5.4 CVSS v3.1 Published 2023-11-20
Fix available
A fix is available. Upgrade to after 5.0.4 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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
The Audio Merchant plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 5.0.4. This is due to missing or incorrect nonce validation on the audio_merchant_save_settings function. This makes it possible for unauthenticated attackers to modify the plugin's settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 Audio Merchant WordPress plugin (versions up to 5.0.4) lacks proper nonce validation on the audio_merchant_save_settings function, allowing unauthenticated attackers to forge administrative requests. By tricking a logged-in administrator into clicking a malicious link, attackers can modify plugin settings and inject persistent malicious scripts (stored XSS).

MitigationUpdate to version 5.0.5 or later which implements proper nonce validation. Until patched, warn administrators against clicking untrusted links and consider temporarily disabling the plugin if high-risk.

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
Audio MerchantWordPress extension
Affected:<= 5.0.4

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 plugin installation and version
    Navigate to WordPress admin > Plugins > Installed Plugins. Look for 'Audio Merchant' or 'Myaudiomerchant Audio Merchant' and note the version number displayed. Alternatively, check the plugin's main PHP file header or readme.txt for the Version field.
    Affected if The plugin is installed and the version is 5.0.4 or lower.
  2. Locate the vulnerable save_settings function
    Access the WordPress site files via FTP or file manager. Navigate to /wp-content/plugins/audio-merchant/ (or similar path). Open the main plugin file and search for 'audio_merchant_save_settings' or 'save_settings'.
    Affected if The function exists in the plugin code, indicating the vulnerable feature is present.
  3. Check for nonce validation in save_settings
    Within the plugin file containing audio_merchant_save_settings, examine the function definition. Look for wp_verify_nonce, check_admin_referer, or similar nonce verification calls at the beginning of the function.
    Affected if No nonce verification is found, or the check is missing entirely before processing settings.
  4. Inspect stored plugin settings for malicious content
    Access the WordPress database (via phpMyAdmin or command line). Query the wp_options table: SELECT * FROM wp_options WHERE option_name LIKE '%audio_merchant%'. Review the option_value fields for script tags, iframe tags, event handlers (onload, onerror), or encoded JavaScript.
    Affected if Stored settings contain suspicious HTML tags such as <script>, <iframe>, or JavaScript event handlers that were not intentionally configured by an administrator.
  5. Review access control on AJAX endpoints
    Check the plugin for wp_ajax_ and wp_ajax_nopriv_ hooks registration. Look for calls registering 'audio_merchant_save_settings' or similar actions. Determine if nopriv users can trigger the settings save.
    Affected if The settings save action is hooked to wp_ajax_nopriv_ or lacks capability checks, allowing unauthenticated requests.

A user is affected if the Audio Merchant plugin version is 5.0.4 or lower AND the save_settings function lacks nonce verification, allowing attackers to inject malicious scripts into plugin settings.

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 a release after 5.0.4
Interim mitigation

Update to version 5.0.5 or later which implements proper nonce validation. Until patched, warn administrators against clicking untrusted links and consider temporarily disabling the plugin if high-risk.

Recommended fix Moderate confidence

Latest version of Audio Merchant plugin (version > 5.0.4)

  1. Check the current version of the Audio Merchant plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate Audio Merchant in the plugin list and verify the current version number
  4. If the installed version is 5.0.4 or lower, update the plugin to the latest available version
  5. To update: either click 'Update Now' if an update is available, or manually download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin settings have not been tampered with and review for any unexpected malicious configurations
  7. Consider implementing additional CSRF protections at the server level (e.g., WordPress nonce verification best practices)

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

Fix this in Audio Merchant Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.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-2023-6197 — 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-2023-6197 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