LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25318: WordPress WiserReview Product Reviews for WooCommerce plugin <= 2.9 - Broken Access Control vulnerability

Missing Authorization vulnerability in Wisernotify team WiserReview Product Reviews for WooCommerce wiser-review allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WiserReview Product Reviews for WooCommerce: from n/a through <= 2.9.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-25318 is a broken access control issue in the WiserReview Product Reviews for WooCommerce WordPress plugin through version 2.9. A logged-in user may be able to perform actions they should not be allowed to perform. The reported impact is limited integrity loss, not data theft or outage.

Executive priority

Prioritize for WooCommerce sites that allow customer, contributor, or other low-privilege logins. The business risk is unauthorized content or configuration changes, not full site compromise based on current evidence. Address during normal vulnerability remediation unless the plugin is widely deployed on revenue-critical stores.

Technical view

The CVE describes CWE-862 Missing Authorization in the wiser-review plugin. CVSS 3.1 is 4.3 with network access, low attack complexity, low privileges required, no user interaction, unchanged scope, no confidentiality or availability impact, and low integrity impact. Sources do not name a fixed version or detailed vulnerable endpoint.

Likely exposure

Exposure is limited to WordPress/WooCommerce sites running WiserReview Product Reviews for WooCommerce version 2.9 or earlier. The attacker profile is a user with some authenticated access, based on PR:L in the CVSS vector.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not listed as KEV in the supplied data. Public details are sparse, so defenders should treat this as a validation and patch-management issue rather than assume known exploitation.

Researcher notes

Evidence confirms missing authorization but does not include endpoint, capability check, proof of concept, or fixed version. Avoid assuming unauthenticated exploitation. Validate through asset inventory and vendor advisories, not offensive testing against production systems without authorization.

Mitigation direction

  • Inventory WordPress sites for the wiser-review plugin and version.
  • Check the vendor or Patchstack page for fixed-version guidance.
  • Update the plugin if a patched version is available.
  • Disable or remove the plugin where it is not business-critical.
  • Limit WordPress accounts to necessary roles only.

Validation and detection

  • Confirm whether WiserReview Product Reviews for WooCommerce is installed.
  • Identify plugin versions and flag version 2.9 or earlier.
  • Review WordPress users with access to the affected site.
  • Check plugin and WordPress logs for unusual authenticated changes.
  • Track the CVE and Patchstack entry for updated remediation details.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-25318 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-25318Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Wisernotify teamWiserReview Product Reviews for WooCommercewiser-review, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.