Security readout for executives and security teams
Plain-English summary
RestrictMate versions before 1.3.0 reportedly let anyone registering an account choose the administrator role. A successful attacker could control the WordPress site, access sensitive information, change content, install software, and disrupt operations without prior credentials or user interaction.
Executive priority
Treat internet-accessible affected sites as an immediate remediation priority. Administrator creation can translate directly into full site takeover. Prioritize version inventory, upgrade, and compromise review; escalate to incident response if an unexplained administrator or privileged session is found.
Technical view
The plugin reportedly trusts a user-supplied role during registration instead of enforcing an allowed role. This authorization failure, classified as CWE-269, enables unauthenticated administrator creation. The supplied CVSS 3.1 score is 9.8 because exploitation is remote, low-complexity, requires no privileges or interaction, and can compromise confidentiality, integrity, and availability.
Likely exposure
Exposure is limited to WordPress sites running RestrictMate before 1.3.0 where the vulnerable account-registration path is accessible. The bundle does not establish installation prevalence, whether registration must be enabled, or whether other controls reliably block the issue.
Exploitation context
The supplied reference is tagged for exploit information, but the bundle provides no evidence of exploitation in the wild, and the CVE is not listed as KEV. The reported weakness is nevertheless directly reachable by unauthenticated attackers and has a low-complexity attack profile.
Researcher notes
The narrative consistently states that versions before 1.3.0 are affected. However, the structured affected-product entry lists only version "0" with a default unaffected status, creating a metadata inconsistency. Confirm the precise affected range with WPScan or subsequent CVE updates. No exploit procedure or reliable detection signature is supplied.
Mitigation direction
- Upgrade RestrictMate to version 1.3.0 or later after confirming vendor guidance.
- Until upgraded, disable RestrictMate or restrict public account registration where operationally acceptable.
- Review all administrator accounts and remove unauthorized users using established incident-response procedures.
- Rotate privileged credentials and WordPress security keys if compromise is suspected.
Validation and detection
- Inventory WordPress sites and identify every installed RestrictMate version.
- Confirm affected installations are upgraded to version 1.3.0 or later.
- Review administrator creation timestamps, identities, and associated registration records for anomalies.
- Check web and authentication logs for unexpected registrations or privileged sessions.
- Verify public registration cannot assign privileged roles after remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-269: 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 lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-13598 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://wpscan.com/vulnerability/05fd8e45-92fa-4ed4-ae59-9a7b7743ea34/CVE reference, WPScan · exploit, vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE mapping pending import
This CVE carries a CWE mapping that will resolve to a full Glexia CWE intelligence page after the official CWE import is complete.