dbcve.org
WpbulkyWordPress extension · Villatheme

CVE-2023-30482

MEDIUM · 5.4 CVSS v3.1 Published 2023-08-08
Fix available
A fix is available. Upgrade to 1.0.10 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
Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in VillaTheme WPBulky plugin <= 1.0.10 versions.

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

Stored XSS vulnerability in VillaTheme WPBulky WordPress plugin versions 1.0.10 and below allows authenticated users with contributor-level permissions or higher to inject malicious JavaScript code into plugin input fields, which persists and executes when other users view the affected pages.

MitigationUpdate WPBulky plugin to the latest version beyond 1.0.10; alternatively, disable the plugin until a patched version is available.

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
WpbulkyWordPress extension
Affected:< 1.0.10

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 WPBulky plugin is installed
    Log in to WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'WPBulky' or 'VillaTheme WPBulky' in the list of installed plugins
    Affected if WPBulky plugin appears in the installed plugins list
  2. Check installed WPBulky version
    In the Plugins list, find WPBulky and locate the version number displayed beneath the plugin name. Alternatively, access the plugin files via FTP or file manager and check the main plugin file (e.g., wpbulky.php) for the 'Version' header in the plugin comments
    Affected if The version number is 1.0.10 or lower, or if the version field shows any value less than 1.0.10
  3. Confirm plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify that WPBulky shows as 'Active' under the plugin status column
    Affected if The plugin is active and running on the site
  4. Identify accessible input fields
    Navigate to the WPBulky plugin settings or frontend components where user input is accepted (such as bulk edit forms, widget settings, or plugin configuration pages). Inspect the page HTML to locate input fields, textareas, or form elements rendered by the plugin
    Affected if Plugin input fields are present and accessible to authenticated users with contributor-level or higher permissions

Your environment is affected if the WPBulky plugin is installed, active, and running version 1.0.10 or lower, allowing authenticated users to inject scripts into plugin 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 1.0.10 or later
Fixed in 1.0.10
Interim mitigation

Update WPBulky plugin to the latest version beyond 1.0.10; alternatively, disable the plugin until a patched version is available.

Recommended fix Moderate confidence

WPBulky version 1.0.10 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the WPBulky plugin by VillaTheme
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, navigate to Plugins > Add New > Upload Plugin and upload the latest version from wordpress.org
  6. 6. After updating, verify the plugin is running version 1.0.10 or later
  7. 7. Clear any site caches if applicable

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

Fix this in Wpbulky Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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