CVE-2026-57318
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 · uneditedSubscriber Sensitive Data Exposure in Site Reviews <= 8.0.11 versions.
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 confidenceThis is an access control vulnerability in the Site Reviews WordPress plugin where subscriber-level authenticated users can access sensitive data they should not have permission to view. The vulnerability likely stems from insufficient capability checks or IDOR (Insecure Direct Object Reference) in the plugin's review retrieval functions, allowing lower-privileged users to read reviews or reviewer data beyond their authorized scope.
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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Site Reviews plugin installationIn WordPress admin, go to Plugins > Installed Plugins and look for 'Site Reviews' or check the plugins directory via file system for /wp-content/plugins/site-reviews/Affected if Site Reviews plugin is installed and active
-
Check installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and look for the version number under the Site Reviews plugin name, or read the main plugin file header at /wp-content/plugins/site-reviews/plugin.php for the 'Version' tagAffected if Version is present and is 8.0.11 or lower (any version before the security patch)
-
Verify subscriber-level user accounts existIn WordPress admin, go to Users and review the role column to identify any users assigned the 'Subscriber' role, or query the wp_usermeta table for meta_key='wp_capabilities' containing 'subscriber'Affected if One or more subscriber-level accounts exist in the WordPress installation
-
Check for unauthorized review accessReview server access logs or WordPress activity logs for API/ajax requests from low-privilege users accessing endpoints like /wp-json/site-reviews/ or admin-ajax.php?action=get_reviews that may indicate review data exfiltrationAffected if AJAX or REST API requests from subscriber users retrieving reviews they should not have access to are present in logs
A user is affected if the Site Reviews plugin version is 8.0.11 or lower AND subscriber-level accounts exist in WordPress, allowing those low-privilege users potential unauthorized access to review data.
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.
From vendor dataUpdate Site Reviews plugin to a version newer than 8.0.11 to obtain the security patch that properly enforces capability checks for data access.
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57318 — 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-2026-57318 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