dbcve.org
Ad Self UpdateApplication · Dovestones

CVE-2026-31014

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-21
Fix available
A fix is available. Upgrade to 4.0.0.5 or later.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
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.

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 confidence

Dovestones AD Self Update versions before 4.0.0.5 contain a CSRF vulnerability where state-changing endpoints lack CSRF token protection. The affected endpoint accepts application/x-www-form-urlencoded data and allows a POST request to be converted to GET while still successfully modifying user account details, enabling attackers to trick authenticated users into unknowingly changing their account information.

MitigationImplement anti-CSRF tokens for all state-changing operations, enforce SameSite cookie attributes, and validate request Origin/Referer headers to prevent cross-site request forgery attacks.

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
Ad Self UpdateApplication
Affected:< 4.0.0.5

CVSS 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
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Dovestones AD Self Update installation and version
    Locate the application installation directory and check for version information in the application metadata, configuration files, or about/help section. Common locations include the program files directory, registry entries, or the application's web interface.
    Affected if The installed version is Dovestones AD Self Update and is earlier than version 4.0.0.5
  2. Locate state-changing endpoints
    Identify endpoints that handle user account modifications such as password changes, profile updates, or user settings. These are typically found in the application's routing configuration or web.xml file.
    Affected if The application contains endpoints that modify user account details without requiring a specific action or parameter that would only be present in a legitimate POST request
  3. Inspect CSRF token implementation
    Examine the identified state-changing endpoints by reviewing the application source code or capturing a legitimate request to see if an anti-CSRF token or token parameter is required and validated for each state-changing operation.
    Affected if The state-changing endpoints do not require or validate a CSRF token parameter in the request
  4. Test request method handling
    Submit a GET request to a state-changing endpoint using the same parameters that would be used in a POST request to see if the action is still performed.
    Affected if A GET request to the state-changing endpoint successfully modifies user account details, indicating the POST requirement can be bypassed

A user is affected if they are running Dovestones AD Self Update version before 4.0.0.5 and the state-changing endpoints lack CSRF token validation or allow GET requests to perform actions intended for POST methods.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 4.0.0.5 or later
Fixed in 4.0.0.5
Interim mitigation

Implement anti-CSRF tokens for all state-changing operations, enforce SameSite cookie attributes, and validate request Origin/Referer headers to prevent cross-site request forgery attacks.

Recommended fix Moderate confidence

4.0.0.5

  1. Upgrade Dovestones AD Self Update to version 4.0.0.5 or later to obtain the CSRF protection fix
  2. After upgrading, verify that the application now requires and validates CSRF tokens for state-changing operations
  3. Test that application/x-www-form-urlencoded POST requests properly validate CSRF tokens
  4. Confirm that GET requests can no longer perform state-changing operations that previously required POST

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ad Self Update Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-31014 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-31014 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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