CVE-2023-4637 in WPvivid Plugin
Summary
by MITRE • 02/06/2024
The WPvivid plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the restore() and get_restore_progress() function in versions up to, and including, 0.9.94. This makes it possible for unauthenticated attackers to invoke these functions and obtain full file paths if they have access to a back-up ID.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 04/11/2026
The WPvivid plugin for WordPress presents a critical security vulnerability classified as CVE-2023-4637, which stems from insufficient access control mechanisms within its core functionality. This vulnerability specifically affects versions up to and including 0.9.94, creating a pathway for unauthorized entities to exploit the plugin's restore capabilities. The flaw manifests through two primary functions: restore() and get_restore_progress(), both of which lack proper capability checks that should verify user authorization before execution. This omission allows attackers to bypass normal authentication requirements and directly invoke these functions, fundamentally undermining the plugin's security posture and exposing sensitive system information.
The technical nature of this vulnerability aligns with CWE-284, which describes improper access control mechanisms in software systems. Attackers can leverage this weakness by obtaining a backup ID, which serves as the primary entry point for exploitation. Once armed with this identifier, unauthenticated users can call the vulnerable functions and potentially extract full file paths from the affected WordPress installation. This information disclosure represents a significant risk as it provides attackers with detailed knowledge of the server's file structure, including directory paths and potential file locations that could be targeted in subsequent attacks. The vulnerability essentially transforms the backup restoration functionality into an information leakage mechanism, where the intended security feature becomes a vector for reconnaissance.
The operational impact of CVE-2023-4637 extends beyond simple information disclosure, creating a foundation for more sophisticated attacks within the target environment. The exposure of full file paths can enable attackers to map the entire WordPress installation structure, identify potentially vulnerable components, and plan more targeted exploitation strategies. This vulnerability particularly affects WordPress environments where WPvivid is installed, making it a prime target for automated scanning tools that specifically look for this type of access control flaw. The implications are severe as it allows attackers to understand the underlying system architecture and potentially identify other vulnerabilities that might exist within the same environment, effectively providing a roadmap for further compromise.
Security mitigation for this vulnerability requires immediate attention from WordPress administrators and system maintainers. The most effective solution involves updating the WPvivid plugin to a version that includes proper capability checks and authentication verification for the affected functions. Organizations should also implement network-level protections such as rate limiting and access controls to prevent automated exploitation attempts. Additionally, security monitoring should be enhanced to detect unusual patterns of backup ID access or function invocation. From an ATT&CK framework perspective, this vulnerability maps to techniques involving privilege escalation and reconnaissance, as attackers can use the exposed file paths to gather intelligence for more advanced attacks. Regular security audits and vulnerability assessments should be conducted to identify similar access control weaknesses in other plugins and themes, as this represents a common pattern in WordPress security vulnerabilities where insufficient authorization checks create dangerous attack vectors.