Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-24634

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-23

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

62/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Authorization Bypass Through User-Controlled Key vulnerability in Rustaurius Ultimate Reviews ultimate-reviews allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Ultimate Reviews: from n/a through <= 3.2.16.

Technical summary

dbcve analysis · moderate confidence

The Ultimate Reviews WordPress plugin versions up to 3.2.16 contains an authorization bypass vulnerability where a user-controlled key allows attackers to exploit incorrectly configured access control security levels. This IDOR-like flaw permits unauthorized users to access or modify review data they should not have permission to access.

MitigationUpdate to the latest version of Ultimate Reviews plugin which contains proper access control validation. If no update is available, restrict plugin access to trusted administrative users until a patch is released.

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

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

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

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Verify Ultimate Reviews plugin is installed

In WordPress admin, go to Plugins > Installed Plugins and look for 'Ultimate Reviews' or 'Ultimate Reviews - Food Reviews' in the list

Affected if The plugin appears in the installed plugins list regardless of activation status
Check installed plugin version

Click on the plugin in the WordPress plugins list to view its details, or check the plugin's main PHP file for the 'Version' header in the plugin comments

Affected if The version number is 3.2.16 or lower (the vulnerability affects versions up to and including 3.2.16)
Confirm plugin is active

In WordPress admin > Plugins, verify the Ultimate Reviews plugin shows as 'Active'

Affected if The plugin is currently active and the version is 3.2.16 or lower
Inspect review submission endpoints

Review the site for any publicly accessible review forms or API endpoints (usually at /?ep=submit_review or similar URL patterns) that accept user-controlled keys or parameters without requiring authentication

Affected if Unauthenticated or low-privilegie users can submit or modify review data through publicly accessible endpoints

A WordPress site is affected if it has Ultimate Reviews plugin version 3.2.16 or lower installed and active, with publicly accessible review submission endpoints that accept user-controlled keys without proper authorization checks.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update to the latest version of Ultimate Reviews plugin which contains proper access control validation. If no update is available, restrict plugin access to trusted administrative users until a patch is released.

Recommended fix Moderate confidence

Latest version of Ultimate Reviews (check WordPress plugin repository for version > 3.2.16)

Check patchstack.com for the specific fixed version of the Ultimate Reviews plugin
Locate the latest version of Rustaurius Ultimate Reviews in the WordPress plugin repository
Upgrade the Ultimate Reviews plugin to the latest available version that contains the security fix
After upgrading, verify that the plugin functions correctly and review user access controls

Caveat Review plugin settings and any custom configurations after upgrade as a precaution

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

Have this fixed Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing3.0 h
Review / QA2.0 h

11.0 hours of engineering $1,930

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

patchstack.com
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24634 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-24634?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 5.3 Medium

Exploit likelihood EPSS, next 30 days 0.2%

Remediation

Need this fixed?

Have this fixed 11 hrs · Moderate

Typical engagement from $1,930

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2026-24634 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References