dbcve.org
Wp RadioWordPress extension · Wpmilitary

CVE-2024-1041

MEDIUM · 5.4 CVSS v3.1 Published 2024-04-10
Fix available
A fix is available. Upgrade to after 3.1.9 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
The WP Radio – Worldwide Online Radio Stations Directory for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's settings in all versions up to, and including, 3.1.9 due to insufficient input sanitization and output escaping as well as insufficient access control on the settings. This makes it possible for authenticated attackers, with subscriber access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 WP Radio WordPress plugin is vulnerable to stored XSS due to insufficient input sanitization and output escaping in its settings functionality. Authenticated users with subscriber-level access can inject arbitrary JavaScript that executes whenever other users access affected pages.

MitigationUpdate the WP Radio plugin to version 3.2.0 or later which contains proper input sanitization, output escaping, and access control fixes.

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
Wp RadioWordPress extension
Affected:<= 3.1.9

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. Verify WP Radio plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'wp-radio' or 'wpmilitary-wp-radio'. Alternatively, log into WordPress admin and look for WP Radio in the Plugins list.
    Affected if The plugin is found installed in the WordPress environment
  2. Determine installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find WP Radio. The version number is displayed in the plugin description. Alternatively, open the main plugin PHP file (e.g., wp-radio/wp-radio.php) and check the 'Version' header in the plugin comments.
    Affected if The displayed version is 3.1.9 or lower
  3. Confirm subscriber-level access is possible
    Check WordPress user roles in Users > All Users. Verify if any user with 'Subscriber' role exists and can log into the site.
    Affected if Subscriber-level accounts exist and can access the WordPress site
  4. Inspect plugin settings for XSS payloads
    Access the WP Radio settings page (usually under Settings > WP Radio or a dedicated WP Radio menu). Examine form fields such as station names, descriptions, or other text inputs. View the page source or inspect stored values to see if unsanitized HTML/JavaScript is present.
    Affected if The settings fields contain unsanitized HTML or JavaScript code that executes when the settings page is viewed

The environment is affected if the WP Radio plugin (wpmilitary wp radio) version 3.1.9 or lower is installed, subscriber-level access exists, and the plugin settings are accessible to subscribers without proper sanitization of input fields.

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 3.1.9
Interim mitigation

Update the WP Radio plugin to version 3.2.0 or later which contains proper input sanitization, output escaping, and access control fixes.

Recommended fix High confidence

3.2.0 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the WP Radio plugin in the list
  4. If an update is available, click 'Update Now' to install the latest version
  5. Alternatively, manually download version 3.2.0 or later from wordpress.org and upload via Plugins > Add New > Upload Plugin
  6. Verify the updated version number reflects 3.2.0 or higher after updating

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

Fix this in Wp Radio Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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