dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-12154

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 weeks old

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 Reviews Widgets for Google, Yelp & TripAdvisor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'page_id' shortcode attribute of the [fbrev] shortcode in versions up to and including 2.7.3. This is due to insufficient input sanitization and output escaping in the Feed_Shortcode::fbrev() method, which passes the raw shortcode attribute through Feed_Old::get_feed() into the View::render() method, where it is echoed directly into the data-id HTML attribute without esc_attr(). This makes it possible for authenticated attackers, with contributor-level 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 Reviews Widgets for Google, Yelp & TripAdvisor WordPress plugin up to version 2.7.3 contains a stored XSS vulnerability in the [fbrev] shortcode's 'page_id' attribute. The Feed_Shortcode::fbrev() method passes the raw shortcode attribute through Feed_Old::get_feed() to View::render(), where it is output directly into a data-id HTML attribute without esc_attr() sanitization, allowing authenticated contributors+ to inject malicious scripts.

MitigationUpdate the plugin to the latest version when available. As an interim measure, ensure only trusted users with contributor-level access or higher are permitted, and consider disabling the [fbrev] shortcode until the patch is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Reviews Widgets for Google, Yelp & TripAdvisor' or check the plugin header in wp-content/plugins/reviews-widget-pack/your-plugin-file.php for the 'Version' field
    Affected if The installed version is 2.7.3 or earlier (any version up to and including 2.7.3)
  2. Detect if [fbrev] shortcode is in use
    Search your WordPress database: SELECT * FROM wp_posts WHERE post_content LIKE '%[fbrev%' AND post_status='publish'; or inspect page source for elements with data-id attributes from shortcode usage
    Affected if The [fbrev] shortcode with a page_id attribute is actively used in published content
  3. Verify contributor+ user access
    In WordPress admin, go to Users and review roles. Check for any user with Contributor, Author, Editor, or Administrator role who is not fully trusted
    Affected if Any untrusted or compromised user account has contributor-level access or higher, allowing them to create content with the vulnerable shortcode
  4. Inspect the vulnerable code path
    Examine the plugin file containing Feed_Shortcode::fbrev() or Feed_Old::get_feed() method and verify if the page_id parameter is output in HTML without esc_attr() sanitization - look for data-id="' . $page_id . '" or similar unsanitized output
    Affected if The plugin code directly outputs the page_id attribute into HTML without passing it through esc_attr() or similar sanitization function

You are affected if your installed plugin version is 2.7.3 or earlier AND you have untrusted users with contributor+ access AND the [fbrev] shortcode is being used on your site, allowing stored XSS injection via the page_id parameter.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest version when available. As an interim measure, ensure only trusted users with contributor-level access or higher are permitted, and consider disabling the [fbrev] shortcode until the patch is applied.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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