Wp SquaredWordPress extension · Cpanel
CVE-2026-32992
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSSL verification is disabled in the DNS Cluster system. This could allow for a malicious server to man-in-the-middle the request and capture credentials.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSSL/TLS certificate verification is disabled in the DNS Cluster system's client connections. This allows an attacker positioned on the network path to intercept and decrypt communications by presenting a fraudulent certificate, enabling credential theft via a classic man-in-the-middle attack.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Wp SquaredWordPress extension
>= 126.1.0, < 136.1.12>= 126.0.0, < 126.0.59>= 130.0.0, < 130.0.23>= 132.0.0, < 132.0.32>= 134.0.0, < 134.0.26>= 136.0.0, < 136.0.10>= 126.0.0, < 126.0.59>= 130.0.0, < 130.0.23>= 132.0.0, < 132.0.32>= 134.0.0, < 134.0.26>= 136.0.0, < 136.0.10CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify DNS Cluster system installationLocate the DNS Cluster client configuration files. Check common paths such as /etc/dns-cluster/, /opt/dns-cluster/config/, or the application's config directory. Look for files named cluster.conf, client.conf, dns-cluster.yaml, or similar.Affected if A DNS Cluster client configuration file exists on the system
-
Locate SSL/TLS verification settingsOpen the DNS Cluster client configuration file and search for keywords related to SSL certificate verification: verify_ssl, ssl_verify, check_cert, verify_cert, tls_verify, validate_cert, or insecure mode settings.Affected if SSL verification settings are present in the configuration
-
Check certificate verification stateExamine the value associated with each SSL verification setting. Look for values such as 'false', 'no', '0', 'disabled', or 'insecure' that explicitly disable certificate verification.Affected if Any SSL verification option is set to disabled, false, no, or insecure
-
Identify client connection endpointsReview the configuration file for outbound connection definitions to external DNS servers, APIs, or management interfaces. Note URLs or hostnames used for these client connections.Affected if The configuration defines outbound client connections to external systems without enforced certificate validation
-
Verify connection securityIf available, use network capture tools or application logs to confirm whether the DNS Cluster client accepts connections without validating server certificates. Check for any warning or debug messages mentioning skipped certificate validation.Affected if Client connections proceed without certificate validation or generate SSL verification warnings
A user is affected if their DNS Cluster client configuration explicitly disables SSL/TLS certificate verification for outbound connections, allowing unauthenticated network interception.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data126.0.59130.0.23132.0.32
Enable SSL certificate verification in all DNS Cluster client configurations and ensure proper certificate validation is enforced for all outbound HTTPS/API connections to prevent credential capture.
Fix this in Wp Squared
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32992 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32992 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data