dbcve.org
Ad PhonebookApplication · Dovestones

CVE-2026-31013

MEDIUM · 6.1 CVSS v3.1 Published 2026-04-21
Fix available
A fix is available. Upgrade to 4.0.1.1 or later.
See remediation →
68/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 ADPhonebook <4.0.1.1 has a reflected cross-site scripting (XSS) vulnerability in the search parameter of the /ADPhonebook?Department=HR endpoint. User-supplied input is reflected in the HTTP response without proper input validation or output encoding, allowing execution of arbitrary JavaScript in the victim's browser.

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 ADPhonebook before version 4.0.1.1 contains a reflected XSS vulnerability in the search parameter of the /ADPhonebook?Department=HR endpoint. User-supplied input is returned in the HTTP response without sanitization or encoding, allowing injection of arbitrary JavaScript that executes in victim browsers.

MitigationImplement input validation to reject malicious patterns and apply output encoding (e.g., HTML entity encoding) when reflecting user input in HTTP responses to prevent script execution.

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 PhonebookApplication
Affected:< 4.0.1.1

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 checks

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

  1. Identify if Dovestones ADPhonebook is installed
    Check for the application by accessing the web server hosting it, or review installed software on Windows servers running IIS or other web servers. Look for 'ADPhonebook' in the application pool or website directory.
    Affected if The application is present and accessible via web browser
  2. Determine the installed version
    Access the application's main page or admin interface, check the 'About' or 'Help' section, or examine the DLL/file version properties in the installation directory (typically found in bin/ADPhonebook.dll or similar assemblies).
    Affected if Version is displayed and is below 4.0.1.1
  3. Verify the vulnerable endpoint exists
    Attempt to access the URL pattern /ADPhonebook?Department=HR in a web browser or via curl: curl -s 'http://[target]/ADPhonebook?Department=HR'
    Affected if The endpoint returns an HTTP 200 response with the Department parameter reflected in the page content
  4. Test for reflected XSS in the Department parameter
    Send a crafted request with a test payload in the Department parameter, such as: curl -s 'http://[target]/ADPhonebook?Department=HR%3Cscript%3Ealert(1)%3C/script%3E' and examine if the raw script tags appear unencoded in the response body.
    Affected if The script tags or other JavaScript syntax appear literally in the HTTP response without HTML entity encoding (e.g., &lt;script&gt; instead of &lt;script&gt;)

You are affected if Dovestones ADPhonebook version is below 4.0.1.1 AND the /ADPhonebook endpoint with the Department parameter is accessible and returns user input without HTML encoding.

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.1.1 or later
Fixed in 4.0.1.1
Interim mitigation

Implement input validation to reject malicious patterns and apply output encoding (e.g., HTML entity encoding) when reflecting user input in HTTP responses to prevent script execution.

Recommended fix Moderate confidence

4.0.1.1

  1. Upgrade Dovestones AD Phonebook to version 4.0.1.1 or later to resolve the reflected XSS vulnerability
  2. After upgrading, verify the fix by testing that the search parameter in /ADPhonebook?Department=HR no longer executes arbitrary JavaScript code
  3. Confirm that proper input validation and output encoding are now applied to user-supplied input in the search parameter

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

Fix this in Ad Phonebook Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-31013 — 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-31013 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