CVE-2024-8277
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 · uneditedThe WooCommerce Photo Reviews Premium plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 1.3.13.2. This is due to the plugin not properly validating what user transient is being used in the login() function and not properly verifying the user's identity. This makes it possible for unauthenticated attackers to log in as user that has dismissed an admin notice in the past 30 days, which is often an administrator. Alternatively, a user can log in as any user with any transient that has a valid user_id as the value, though it would be more difficult to exploit this successfully.
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 confidenceThe WooCommerce Photo Reviews Premium plugin fails to properly validate user transients in its login() function, allowing unauthenticated attackers to bypass authentication by exploiting transients associated with users who dismissed admin notices within 30 days, or any user with a valid user_id transient value.
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< 1.3.14CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed plugin versionAccess your WordPress plugins directory and locate the Villatheme Woocommerce Photo Reviews plugin folder, then read the main plugin file (usually photo-reviews.php or similar) to find the version number defined in the plugin headerAffected if The installed version is less than 1.3.14 (such as 1.3.13, 1.3.12, etc.)
-
Locate the vulnerable login() functionIn the plugin directory, search for a function named 'login' within the plugin PHP files, typically found in includes/ or classes/ foldersAffected if The login() function exists in the plugin code and contains logic handling transients without proper user validation
-
Inspect transient handling in the login functionExamine the login() function code for transient get/set operations, specifically looking for code that retrieves transients using user identifiers without validating the current user sessionAffected if The login() function processes transients containing user_id values (such as those created when users dismiss admin notices) and uses these values to authenticate without proper validation
-
Check for active transients in the WordPress databaseQuery the wp_options table or use WP-CLI 'wp transient list' command to examine transients with keys containing 'photo_reviews' or user-related identifiersAffected if There are active transients in the database associated with this plugin that contain user_id values, particularly those created within the last 30 days from dismissed admin notices
Your environment is affected if the Villatheme Woocommerce Photo Reviews plugin version is below 1.3.14 and the login() function handles transients without validating user sessions, allowing unauthenticated access through transient-based authentication bypass.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.3.14
Update to version 1.3.13.3 or later which contains proper transient validation; if no update is available, remove the plugin and seek an alternative review solution.
1.3.14
- Backup your WordPress site and database before making any changes
- Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
- Find 'WooCommerce Photo Reviews' (or 'WooCommerce Photo Reviews Premium') in the plugin list
- Click 'Update now' if an update is available, or manually upload version 1.3.14 of the plugin
- Verify the plugin version has been updated to 1.3.14 or later
- Test that authentication functionality works correctly by logging in as different user types
- Confirm the vulnerability is no longer exploitable by reviewing login logs
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8277 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-8277 in production — separate from our analysis above.
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.
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.
- 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