CVE-2025-0994
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 · uneditedTrimble Cityworks versions prior to 15.8.9 and Cityworks with office companion versions prior to 23.10 are vulnerable to a deserialization vulnerability. This could allow an authenticated user to perform a remote code execution attack against a customer’s Microsoft Internet Information Services (IIS) web server.
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 confidenceTrimble Cityworks contains a deserialization vulnerability in its IIS-hosted web application that allows authenticated users to execute arbitrary code remotely on the server. The vulnerability stems from unsafe deserialization of user-supplied data without proper validation.
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< 15.8.9>= 23.0, < 23.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Confirm Cityworks installationLocate the Cityworks installation directory, typically under the IIS web root (often C:\inetpub\wwwroot\Cityworks\ or similar). Check for the presence of Cityworks DLL files or the Cityworks web application structure.Affected if Cityworks is not installed on the server.
-
Identify Cityworks versionLocate the version information in the Cityworks installation. Common locations include: a Version.txt or version.config file in the installation directory, or check the assembly version of Cityworks DLLs (e.g., Axem.Core.dll). In IIS, you may also find version details in the web.config file or assembly metadata.Affected if The installed version is less than 15.8.9, or is 23.0 through 23.9.x.
-
Check for Office Companion moduleDetermine if the Office Companion feature is installed. This typically appears as an additional application or module within the Cityworks IIS site (often under a /OfficeCompanion or similar path). Check IIS Manager for additional applications under the Cityworks site, or look for Office Companion-specific DLLs or config files in the installation.Affected if Office Companion is installed AND the version is 23.0 through 23.9.x.
-
Verify IIS is the hosting platformConfirm that Cityworks is running on Microsoft IIS. Check IIS Manager for the Cityworks site, or inspect the Windows Services for IIS-related processes. The vulnerability specifically targets the IIS web server hosting Cityworks.Affected if Cityworks is not hosted on Microsoft IIS.
-
Confirm authentication is enabledReview IIS authentication settings for the Cityworks application. Check if Forms Authentication, Windows Authentication, or another authentication method is enabled in IIS Manager under the Cityworks site. The vulnerability requires authenticated access.Affected if Anonymous authentication is the only enabled method and no user accounts exist in Cityworks.
The server is affected if Cityworks (or Cityworks with Office Companion) is hosted on IIS and the installed version falls below 15.8.9 or within the 23.0 to 23.9.x range.
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.
dbcve · scoped15.8.923.10
Upgrade Cityworks to version 15.8.9 or later, or Cityworks with Office Companion to version 23.10 or later. Alternatively, restrict network access to the application and enforce strict authentication controls to limit exposure to authenticated attackers.
15.8.9 or 23.10 (depending on which release branch is in use)
- Identify the currently installed Cityworks version by checking the About or version information in the Cityworks administration interface
- If running a version < 15.8.9, upgrade to version 15.8.9 or later
- If running version 23.0 through 23.09, upgrade to version 23.10 or later
- After upgrading, verify the new version is running correctly and test critical workflows
- Ensure the upgrade is performed during a planned maintenance window with proper backups in place
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,816.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0994 — 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-2025-0994 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