dbcve.org
Rate My PostWordPress extension · Blazzdev

CVE-2024-32823

MEDIUM · 5.3 CVSS v3.1 Published 2024-04-24
Fix available
A fix is available. Upgrade to 3.4.5 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Authorization Bypass Through User-Controlled Key vulnerability in FeedbackWP Rate my Post – WP Rating System.This issue affects Rate my Post – WP Rating System: from n/a through 3.4.4.

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

This is an authorization bypass vulnerability where an attacker can manipulate a user-controlled key (likely a parameter or ID) to access functionality or data they shouldn't have permission to access. The vulnerability exists in the WordPress plugin 'Rate my Post – WP Rating System' versions up to 3.4.4, allowing unauthorized users to bypass authorization checks.

MitigationUpdate the plugin to the latest version which should contain a fix for this authorization bypass. If no update is available, audit the plugin code for improper use of user-supplied input in authorization decisions and implement proper capability checks.

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
Rate My PostWordPress extension
Affected:< 3.4.5

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 Rate My Post plugin is installed
    Log into WordPress admin, navigate to Plugins > Installed Plugins, or inspect the directory wp-content/plugins/rate-my-post/
    Affected if The plugin directory exists in the WordPress installation
  2. Determine installed plugin version
    In WordPress admin, click on the plugin name to view version details, or open the main plugin file (usually rate-my-post.php) and locate the 'Version' header in the plugin comment block
    Affected if Version number is visible and less than 3.4.5
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify the plugin shows as 'Active' under the status column
    Affected if Plugin is currently activated in WordPress
  4. Compare against affected version range
    Compare your installed version to the affected range: versions below 3.4.5 are vulnerable
    Affected if Installed version is 3.4.4 or lower

If Rate My Post plugin is installed, active, and running version 3.4.4 or lower, your environment is affected by this authorization bypass vulnerability.

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 3.4.5 or later
Fixed in 3.4.5
Interim mitigation

Update the plugin to the latest version which should contain a fix for this authorization bypass. If no update is available, audit the plugin code for improper use of user-supplied input in authorization decisions and implement proper capability checks.

Recommended fix Moderate confidence

Rate My Post (FeedbackWP) version 3.4.5 or later

  1. 1. Backup your WordPress site database and files before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. 3. Find 'Rate my Post – WP Rating System' (also known as FeedbackWP) in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 3.4.5 or later
  5. 5. After updating, verify the plugin version shows 3.4.5 or higher under the plugin name
  6. 6. Test the rating submission functionality to ensure the plugin is working correctly after the update

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

Fix this in Rate My Post Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.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-2024-32823 — 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-2024-32823 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