Security readout for executives and security teams
Plain-English summary
Someone with a valid site-to-site transfer key can make a vulnerable WPvivid plugin create its log file in an attacker-chosen writable directory, including the web root. The attacker cannot choose arbitrary file contents, and the filename retains a fixed suffix. The supplied evidence does not establish code execution.
Executive priority
Treat remediation as urgent for affected, internet-accessible sites, especially where transfer keys were used or may be exposed. The critical score warrants prompt inventory and upgrade, although the documented primitive is constrained and active exploitation is not established.
Technical view
WPvivid before 0.9.131 uses an unsanitized unauthenticated request value when constructing a log path, creating a CWE-22 path-traversal condition. Exploitation requires possession of a site-to-site transfer key. The write is limited to existing writable directories, a fixed filename suffix, and WPvivid’s standard log header.
Likely exposure
Exposure is limited to WordPress sites running WPvivid versions earlier than 0.9.131 where an attacker can obtain a usable site-to-site transfer key. Internet-accessible installations, previously shared transfer keys, and web roots writable by the application increase practical risk.
Exploitation context
The bundle marks this CVE as absent from KEV and provides no evidence of exploitation in the wild. WPScan is tagged as containing exploit information, but that does not establish active exploitation. A valid site-to-site transfer key is still required despite no WordPress account being needed.
Researcher notes
The described primitive supports controlled file location, not arbitrary filename or content. No source establishes remote code execution. The structured affected record lists vendor as Unknown, version “0,” and default status unaffected, conflicting with the title’s pre-0.9.131 boundary; validate product metadata against WPScan and vendor guidance.
Mitigation direction
- Upgrade WPvivid to version 0.9.131 or later, after confirming current vendor guidance.
- Prioritize installations that have used site-to-site transfers or may have exposed transfer keys.
- Restrict application write permissions, particularly within the web root, as defense in depth.
- Follow vendor procedures to revoke or replace any transfer key suspected of exposure.
Validation and detection
- Inventory every WordPress site and identify WPvivid installations earlier than version 0.9.131.
- Confirm remediated installations report WPvivid version 0.9.131 or later.
- Determine whether site-to-site transfer keys were configured, shared, logged, or otherwise exposed.
- Inspect writable directories for unexpected files bearing WPvivid’s fixed suffix and standard log header.
- Review application and request logs for suspicious send_to_site_connect activity.
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-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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 lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell 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-19725 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.1 (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:N
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:N3.95.2CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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/999889f4-f8be-4b44-b665-1a94df8d050d/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.
Improper Limitation of a Pathname to a Restricted Directory
Improper Limitation of a Pathname to a Restricted Directory represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.