Customer Reviews For WoocommerceWordPress extension · Cusrev

CVE-2024-1044

MEDIUM · 5.3 CVSS v3.1 Published 2024-02-29

Fix available

A fix is available. Upgrade to 5.39.0 or later.

See remediation →

62/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

The Customer Reviews for WooCommerce plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'submit_review' function in all versions up to, and including, 5.38.12. This makes it possible for unauthenticated attackers to submit reviews with arbitrary email addresses regardless of whether reviews are globally enabled.

Technical summary

dbcve analysis · high confidence

The Customer Reviews for WooCommerce plugin has a missing capability check on the submit_review function, allowing unauthenticated users to submit reviews with arbitrary email addresses regardless of whether reviews are globally enabled. This is a Broken Access Control vulnerability (CWE-862).

MitigationUpdate to version 5.38.13 or later which includes proper capability/authorization checks on the submit_review function.

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

Affected products & versions

NVD · CPE data

Customer Reviews For WoocommerceWordPress extension

Affected:< 5.39.0

CVSS breakdown

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?

dbcve checks

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

Confirm WooCommerce is installed

Check your WordPress plugins page or inspect wp-content/plugins/ for woocommerce directory

Affected if WooCommerce is not present - this CVE only affects environments with WooCommerce installed
Confirm Customer Reviews for WooCommerce plugin is installed

Check your WordPress plugins page or inspect wp-content/plugins/ for customer-reviews-for-woocommerce or similar directory name

Affected if The plugin is not installed - this CVE only applies when the vulnerable plugin is present
Identify the installed plugin version

Navigate to WordPress admin > Plugins > Customer Reviews for WooCommerce and read the version number from the plugin description, or check the version header in the main plugin PHP file

Affected if Unable to determine version - cannot assess vulnerability status
Compare installed version against affected range

Compare the identified version number to the affected range: versions prior to 5.39.0 are vulnerable

Affected if Installed version is 5.38.x or lower (anything below 5.39.0)

The environment is affected if WooCommerce and the Customer Reviews for WooCommerce plugin are both installed with a version lower than 5.39.0

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 5.39.0 or later

Fixed in 5.39.0

Interim mitigation

Update to version 5.38.13 or later which includes proper capability/authorization checks on the submit_review function.

Recommended fix High confidence

5.39.0

Log in to the WordPress admin dashboard
Navigate to the Plugins section
Locate 'Customer Reviews for WooCommerce' in the installed plugins list
Click 'Update now' if an update is available, or manually upload version 5.39.0 or higher
Verify the plugin updated successfully to version 5.39.0 or later
Test that the review submission functionality works correctly with proper access controls

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

Fix this in Customer Reviews For Woocommerce Scoped from the published advisory

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

9.0 hours of engineering $1,570

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,512.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

www.wordfence.comThird Party Advisory
plugins.trac.wordpress.orgProduct
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2024-1044?

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 existsUpgrade to 5.39.0 or later

Severity 5.3 Medium

Exploit likelihood EPSS, next 30 days 0.4%

Affects: Customer Reviews For Woocommerce

Remediation

Need this fixed?

Fix this in Customer Reviews For Woocommerce 9 hrs · Moderate

Typical engagement from $1,570

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2024-1044 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.

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.

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

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References