dbcve.org
Nice BackgroundsWordPress extension · Brx8r

CVE-2024-49330

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-20
Fix available
A fix is available. Upgrade to after 1.0 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
Unrestricted Upload of File with Dangerous Type vulnerability in brx8r Nice Backgrounds nicebackgrounds allows Upload a Web Shell to a Web Server.This issue affects Nice Backgrounds: from n/a through <= 1.0.

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

The Nice Backgrounds plugin for WordPress contains an unrestricted file upload vulnerability that allows attackers to upload dangerous file types, including web shells, directly to the web server. This vulnerability stems from insufficient validation of uploaded file types, allowing executable scripts to be stored in publicly accessible web directories.

MitigationImplement strict server-side file type validation using magic byte inspection, whitelist approved file extensions, store uploads outside the web root, and disable script execution in upload directories.

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
Nice BackgroundsWordPress extension
Affected:<= 1.0

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
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Check if Nice Backgrounds plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Nice Backgrounds' or 'Brx8r Nice Backgrounds', or inspect the /wp-content/plugins/ directory for a folder named 'nice-backgrounds' or similar.
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed plugin version
    In WordPress admin, click on the Nice Backgrounds plugin to view its details, or open the main plugin PHP file and look for the 'Version' header in the plugin comments.
    Affected if The version is 1.0 or any version where the number is less than or equal to 1.0
  3. Locate the upload directory
    Inspect the plugin settings page in WordPress admin under the Nice Backgrounds plugin options, or check the plugin source code for upload path configuration.
    Affected if Uploads are stored within the /wp-content/uploads/ directory or any web-accessible location
  4. Verify upload directory is web-accessible
    Attempt to access the upload directory via a web browser (e.g., visit yoursite.com/wp-content/uploads/nice-backgrounds/ or the path configured in plugin settings).
    Affected if The directory is accessible and files can be downloaded or executed via HTTP
  5. Check if script execution is allowed in upload directories
    Check the .htaccess file in the upload directory for directives blocking script execution (Options -Indexes, RemoveHandler, php_flag, etc.), or test by uploading a simple PHP file and attempting to execute it.
    Affected if No security restrictions exist in the upload directory .htaccess and uploaded PHP/ASP/JSP files can be executed via browser

A user is affected if the Nice Backgrounds plugin version is 1.0 or lower, uploads are stored in a web-accessible directory, and script execution is not blocked in that directory.

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.

From vendor data
Upgrade available Upgrade to a release after 1.0
Interim mitigation

Implement strict server-side file type validation using magic byte inspection, whitelist approved file extensions, store uploads outside the web root, and disable script execution in upload directories.

Fix this in Nice Backgrounds Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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