dbcve.org
Opal Hotel Room BookingWordPress extension · Wpopal

CVE-2022-29449

MEDIUM · 5.4 CVSS v3.1 Published 2022-05-19
Fix available
A fix is available. Upgrade to after 1.2.7 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
Authenticated (contributor or higher user role) Stored Cross-Site Scripting (XSS) vulnerability in Opal Hotel Room Booking plugin <= 1.2.7 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

Authenticated stored XSS in Opal Hotel Room Booking plugin <=1.2.7 allows contributor+ users to inject malicious JavaScript into booking fields that persists and executes when other users view the booking pages.

MitigationUpdate Opal Hotel Room Booking plugin to version 1.2.8 or later which patches the stored XSS vulnerability.

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
Opal Hotel Room BookingWordPress extension
Affected:<= 1.2.7

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. Identify Opal Hotel Room Booking plugin installation
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and locate 'Opal Hotel Room Booking' or 'Wpopal Opal Hotel Room Booking' in the list
    Affected if The plugin is not found in the installed plugins list, indicating the plugin is not present in the environment
  2. Determine installed plugin version
    In the plugins list, locate the version number displayed beneath the plugin name 'Opal Hotel Room Booking'
    Affected if The displayed version number is 1.2.7 or lower (any version up to and including 1.2.7)
  3. Verify plugin is active
    In WordPress admin > Plugins, confirm the plugin status shows as 'Active'
    Affected if The plugin is active and running
  4. Confirm contributor or higher role exists
    Navigate to WordPress admin > Users and review user roles assigned to accounts. Identify any users with 'Contributor', 'Author', 'Editor', or 'Administrator' roles
    Affected if At least one user account possesses Contributor-level permissions or higher, enabling access to booking creation features
  5. Check for existing bookings
    Access the booking management area (typically under 'Opal Hotel' menu in admin dashboard) and review whether any bookings have been created
    Affected if Bookings exist in the system, as this indicates the vulnerable feature is in use and any injected scripts would execute upon page view

Environment is affected if Opal Hotel Room Booking plugin is installed with version 1.2.7 or lower, is active, and the booking feature is accessible to users with Contributor-level permissions or higher.

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

Update Opal Hotel Room Booking plugin to version 1.2.8 or later which patches the stored XSS vulnerability.

Recommended fix Moderate confidence

Version 1.2.8 or later (update to latest available version)

  1. 1. Log in to the WordPress admin dashboard with a contributor or higher user role
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Opal Hotel Room Booking' plugin in the list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from wordpress.org and upload it via Plugins > Add New > Upload Plugin
  6. 6. Verify the update completed successfully

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

Fix this in Opal Hotel Room Booking Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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