Pie Register <= 3.8.4.15 - Unauthenticated Plugin Settings Reset and Redirect Data Destruction
CVSS score
—
EPSS probability
—
Risk score
—
Published
2 h ago
Resmî kaynaklarda yeterli kanıt bulunamadı. Bu sonuç “yama yok” anlamına gelmez.
Impact on My Inventory
Only the personal products you have added to your account are assessed; an organisation's inventory does not appear here.
Checking session…
Vulnerability description
DayBreach AI Explanation
Verified against sourcesSources read
1
Source agreement
Tam uyum
Evidence confidence
%55
Short explanation
The Pie Register WordPress plugin through version 3.8.4.15 lacks capability, nonce, and authentication checks on a request handler, allowing unauthenticated attackers to reset the plugin's settings to defaults and destroy its data table (S0,S1).
Disabling registration security controls and deleting registration data undermines site integrity and user trust (S0).
What should be done?
- Apply the vendor advisory when a fix is released
- Upgrade the plugin to a patched version or temporarily disable it
- Filter the vulnerable endpoint with a Web Application Firewall
- Monitor request logs for unauthorized access attempts
Chain of evidence and sources
Pie Register 3.8.4.15 ve öncesi, yetki, nonce veya kimlik doğrulama kontrolü olmayan bir istek işleyicisi içerir (S0).
Kimlik doğrulaması olmayan bir saldırgan, bu işleyiciyi kullanarak eklentinin ayarlarını varsayılanlara sıfırlayabilir (S0,S1).
Aynı işleyici, eklentinin veri tablosunu yok ederek tüm kayıt verilerini silebilir (S0,S1).
Yama durumu resmi kaynaklarda doğrulanamadı; mevcut bir düzeltme olup olmadığı belirsizdir (S0).
Show the technical text from the sources
The Pie Register WordPress plugin through 3.8.4.15 does not perform any capability, nonce or authentication check on one of its request handlers, allowing unauthenticated attackers to reset the Pie Register WordPress plugin through 3.8.4.15's settings to their defaults (disabling registration security controls such as new-user email verification) and to destroy a Pie Register WordPress plugin through 3.8.4.15 data table.
This explanation was compiled automatically from the source records. Scores, active exploitation, patch and exploit status come straight from the sources.
IMPACT: Affected Products and Software
Affected Products
The following products are affected by CVE-2026-96961 vulnerability. Where our threat engine knows the exact affected versions, they are listed below.
| ID | VENDOR | PRODUCT | ACTION |
|---|---|---|---|
| 1 | Unknown | Pie Register | View |
RED HAT CSAF/VEX: Product Impact Check
SCORING: CVSS from Multiple Sources
CVSS Scores
The Common Vulnerability Scoring System is a standardised framework for assessing the severity of vulnerabilities in software and systems. We collect and display CVSS scores from several sources for each CVE.
| SCORE | VERSION | SEVERITY | VECTOR | SOURCE |
|---|---|---|---|---|
| The sources have not yet published a verified CVSS metric. | ||||
Patch and Remediation Guide
Solution & Remediation Advisory
İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.
Public exploit and active exploitation status
Verified exploit intelligence
No verified public PoC, exploit repository or Metasploit module has been found for this CVE yet.
Weakness Classification and Attack Patterns (CWE & CAPEC)
CWE - Common Weakness Enumeration
While CVE identifies specific instances of vulnerabilities, CWE categorises the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-96961 is associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-96961 weaknesses.
Official Sources and Advisories
Yama durumu bilinmiyor
Similar Vulnerabilities
Get this vulnerability through the API
Affected products, version ranges, exploitation status and patch information in a single request, with a free key.
curl -H "x-api-key: $DAYBREACH_API_KEY" \ "https://api.daybreach.dev/api/v1/intel/cves/CVE-2026-96961"