dbcve.org
Hotel BookingWordPress extension · Nicdark

CVE-2022-29443

MEDIUM · 5.4 CVSS v3.1 Published 2022-06-15
Fix available
A fix is available. Upgrade to after 3.0 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
Multiple Authenticated (contributor or higher user role) Stored Cross-Site Scripting (XSS) vulnerabilities in Nicdark's Hotel Booking plugin <= 3.0 at WordPress.

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 vulnerabilities in Nicdark's Hotel Booking plugin for WordPress (versions 3.0 and below) allow authenticated users with contributor or higher roles to inject malicious JavaScript into the application. The injected scripts persist and execute when other users view the affected content.

MitigationUpdate the Nicdark Hotel Booking plugin to the latest patched version. Review and sanitize all user inputs and outputs across the plugin to prevent XSS.

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
Hotel BookingWordPress extension
Affected:<= 3.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
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. Confirm plugin installation and version
    Access WordPress admin > Plugins > Installed Plugins and locate 'Nicdark Hotel Booking'. Note the installed version number. Alternatively, check the plugin header file at /wp-content/plugins/nicdark-hotel-booking/nicdark-hotel-booking.php for the 'Version' property, or run: wp plugin list --name='nicdark-hotel-booking'
    Affected if Plugin is installed with version 3.0 or lower
  2. Identify users with contributor or higher roles
    Navigate to WordPress admin > Users > All Users. Review the 'Role' column for any accounts assigned 'Contributor', 'Author', 'Editor', or 'Administrator' roles. These roles have the capability required to exploit the flaw.
    Affected if At least one user account exists with contributor role or higher
  3. Inspect plugin-generated database tables for suspicious content
    Access the WordPress database via phpMyAdmin or WP-CLI (wp db query). Examine tables prefixed with the plugin's custom tables, typically containing booking, room, or hotel-related data. Look for script tags, javascript: URLs, or HTML event handlers in text fields.
    Affected if Stored XSS payloads (script tags, event handlers) are present in plugin-specific database fields
  4. Review plugin admin panels for stored XSS indicators
    Navigate through the plugin's admin interfaces (typically under 'Hotel Booking' menu items). Inspect form fields for booking names, room descriptions, pricing, or customer data. Check if unsanitized HTML or scripts render in the browser.
    Affected if Plugin admin interfaces display unescaped HTML or JavaScript when rendering stored data

Your environment is affected if the Nicdark Hotel Booking plugin is installed at version 3.0 or below and any user with contributor-level or higher access exists, or if malicious scripts are already stored in plugin database 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.

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

Update the Nicdark Hotel Booking plugin to the latest patched version. Review and sanitize all user inputs and outputs across the plugin to prevent XSS.

Fix this in Hotel Booking 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-2022-29443 — 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-29443 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