Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-75903 Overview
The Vulnity Security plugin for WordPress contains an authentication bypass vulnerability affecting all versions up to and including 1.4.3. The flaw stems from insufficient protection of the delegated-login pairing credential file on Nginx-based installations. The plugin's generated server configuration snippet guards the wrong directory path, exposing the credential file to unauthenticated requests. Attackers who retrieve the stored credentials can forge signed REST API requests and authenticate as an administrator. The vulnerability is tracked under CWE-287 (Improper Authentication).
Critical Impact
Unauthenticated attackers can retrieve pairing credentials from Nginx-hosted WordPress sites and gain full administrator access through forged REST API requests.
Affected Products
- Vulnity Security plugin for WordPress — all versions through 1.4.3
- Nginx-based WordPress installations running the plugin
- WordPress sites using the delegated-login pairing feature
Discovery Timeline
- 2026-10-16 - CVE-2026-75903 published to NVD
- 2026-10-16 - Last updated in NVD database
Technical Details for CVE-2026-75903
Vulnerability Analysis
The Vulnity Security plugin ships a delegated-login workflow that stores a pairing credential on disk. On Apache deployments, .htaccess rules restrict access to the credential file. On Nginx deployments, the plugin generates a server configuration snippet administrators are expected to include in their site configuration.
The generated snippet references the wrong directory path. As a result, the location block never matches the actual file location, and Nginx serves the credential file as a static asset to any unauthenticated requester. Once an attacker reads the pairing credential, they can sign REST API requests that the plugin accepts as originating from a trusted delegated-login partner, promoting the session to administrator.
Root Cause
The root cause is a path mismatch in the Nginx hardening snippet generated by class-static-security.php. The guard protects a directory that does not correspond to where the plugin writes the credential file. Access controls therefore fail silently without producing an error at plugin activation or runtime.
Attack Vector
Exploitation is remote and unauthenticated. An attacker issues a direct HTTP GET request to the credential file's URL on a vulnerable Nginx-hosted site. After obtaining the shared secret, the attacker crafts a signed request to the plugin's delegated-login REST endpoint. The server validates the signature against the stolen credential and returns an authenticated administrator session.
The attack complexity is elevated because successful exploitation requires the target to run Nginx and expose the credential path, but no user interaction or prior authentication is required. Review the Wordfence Vulnerability Report and the WordPress Plugin Security Change for the corrected path handling.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-75903
Indicators of Compromise
- Unexpected HTTP GET requests from external IPs to Vulnity plugin directories under wp-content/plugins/vulnity/
- Successful 200 responses to requests for pairing credential files that should return 403
- New administrator accounts or privilege changes without corresponding wp-login.php activity
- Signed REST API calls to Vulnity delegated-login endpoints originating from unknown IP addresses
Detection Strategies
- Review Nginx access logs for requests targeting Vulnity plugin paths that return HTTP 200 instead of 403 or 404
- Correlate REST API calls to /wp-json/vulnity/ endpoints against the IP addresses of legitimate delegated-login partners
- Audit WordPress user tables for administrator role assignments that do not match a known login event
Monitoring Recommendations
- Enable WordPress audit logging to capture administrator role changes and REST API authentication events
- Alert on direct HTTP access to any file under the Vulnity plugin's data directory from untrusted networks
- Monitor the Nginx configuration file for drift from the vendor-approved hardening snippet in version 1.4.4
How to Mitigate CVE-2026-75903
Immediate Actions Required
- Upgrade the Vulnity Security plugin to version 1.4.4 or later on all WordPress installations
- Rotate any delegated-login pairing credentials issued before the upgrade
- Review administrator accounts and remove any that cannot be attributed to a legitimate user
- Inspect the active Nginx configuration and replace the outdated plugin-generated snippet with the corrected version
Patch Information
The maintainers addressed the vulnerability in Vulnity Security 1.4.4. The fix corrects the directory path referenced in the Nginx hardening snippet so that location directives match the credential file. Refer to the WordPress Plugin Changeset Update for the full diff between 1.4.3 and 1.4.4.
Workarounds
- Manually add an Nginx location block that denies all access to the plugin's credential directory until the upgrade is applied
- Disable the Vulnity Security plugin on Nginx-hosted sites that cannot be patched immediately
- Place the WordPress site behind a web application firewall rule that blocks direct requests to plugin data paths
# Example Nginx hardening block (apply until upgrade to 1.4.4)
location ~* /wp-content/plugins/vulnity/.*\.(json|key|txt)$ {
deny all;
return 403;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

