● Medium · CVSS 6.3

How to Fix CVE-2026-31014: n/a in n/a

Q: Is CVE-2026-31014 being exploited in the wild?

As of 2026-05-25, CVE-2026-31014 is not listed in the CISA Known Exploited Vulnerabilities catalog. Watch the catalog and patch on a normal cadence; KEV status can change as exploitation evidence emerges.

Q: What is the CVSS score for CVE-2026-31014?

The CVSS base score is 6.3 (Medium).

Q: What version fixes this?

The vendor advisory names the patched build. See the References section.

Q: Will a WAF or IDS rule alone close this?

No. Network filters cut down opportunistic scans but they do not remove the flaw. The vendor patch is the only durable fix.

By Sai Kiran Pandrala

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-3334: SQL Injection in CMS Commander – Manage Multiple Sites — SQL Injection in CMS Commander – Manage Multiple Sites
How to Fix CVE-2026-27449: Improper access control in Umbraco.Engage.Forms — Improper access control in Umbraco.Engage.Forms
How to Fix CVE-2026-6105: Improper authorization in go-fastdfs-web , Improper authorization in go-fastdfs-web
How to Fix CVE-2026-32958: Use of hard-coded cryptographic key in AMC Manager , Use of hard-coded cryptographic key in AMC Manager
How to Fix CVE-2026-45666: Insecure Direct Object Reference in open-webui , Insecure Direct Object Reference in open-webui

Last verified: 2026-05-25

CVE-2026-31014 is a n/a in n/a n/a. Fix it by upgrading to the patched build from the vendor advisory.

⚡ At a glance


Severity	CVSS 6.3 - Medium
Actively exploited?	Not currently in the CISA KEV catalog
Affected	n/a n/a
Fixed in	See vendor advisory
Type (CWE)	n/a

What is CVE-2026-31014?

CVE-2026-31014 is a n/a flaw in n/a n/a. It carries a CVSS base score of 6.3 (medium). It is not currently listed in the CISA Known Exploited Vulnerabilities catalog.

From the source record: Dovestones Softwares AD Self Update <4.0.0.5 is vulnerable to Cross Site Request Forgery (CSRF). The affected endpoint processes state-changing requests without requiring a CSRF token or equivalent protection. The endpoint accepts application/x-www-form-urlencoded requests, and an originally POST-based request can be converted to a GET request while still successfully updating user details. This allows an attacker to craft a malicious request that, when visited by an authenticated user, can modify user account information without their consent.

Why it matters in practice: The blast radius depends on how the affected service is exposed. An internet-facing instance with no compensating controls is the highest-risk configuration.

Am I affected?

You are affected if your installation of n/a matches a version listed in the Affected row above.

Check the running version against the Affected row above using the product's admin console or --version flag.

How to fix CVE-2026-31014

Apply the vendor patch. Target the build named in the Fixed in row above (See vendor advisory). The runnable command set below covers the most common deployment patterns for n/a.

Generic upgrade pattern

If the affected product is a Linux package, upgrade via the system package manager:


# Debian / Ubuntu
sudo apt-get update && sudo apt-get upgrade -y

# RHEL / Rocky / Alma
sudo dnf upgrade --security -y

If it ships as a Windows installer, download the patched build from the vendor advisory and:


# Vendor advisory: https://dovestones.com/download/
Start-Process msiexec.exe -ArgumentList '/i <patched-installer>.msi /qn /norestart' -Wait
Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | \
    Where-Object DisplayName -match '<product-name>' | Select-Object DisplayName, DisplayVersion

After applying the patch

Restart the service or device so the patched binary loads.
Confirm the running version matches the Fixed in row using the verification command below.
Rotate credentials and API keys that the affected service could access if the asset was exposed during the disclosure window.

If you can't patch immediately

Until the patch lands, narrow the attack surface with these runnable controls.

Restrict network exposure

Block public access to the affected service at the perimeter. Allow only trusted source IPs.


# Linux iptables: only allow trusted admin subnet
sudo iptables -A INPUT -p tcp --dport 443 -s 10.10.10.0/24 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 443 -j DROP
sudo iptables-save | sudo tee /etc/iptables/rules.v4


# Windows firewall: only allow trusted admin subnet on management port
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Allow" -Direction Inbound -Action Allow `
  -RemoteAddress 10.10.10.0/24 -Protocol TCP -LocalPort 443
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Deny"  -Direction Inbound -Action Block `
  -Protocol TCP -LocalPort 443

Mitigations are temporary. Apply the vendor patch as soon as a maintenance window opens.

How to verify the fix worked

Confirm the patched build is the one actually running.

Check the running version against the Affected row above using the product's admin console or --version flag.

Expected: a version at or above the patched build named in the vendor advisory.

Also worth doing: pull recent log windows for indicators of compromise listed in the vendor advisory, and re-run an authenticated vulnerability scan with up-to-date signatures.

Frequently asked questions

Is CVE-2026-31014 being exploited in the wild?