CVE-2025-15563
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 · uneditedAny unauthenticated user can reset the WorkTime on-prem database configuration by sending a specific HTTP request to the WorkTime server. No authorization check is applied here.
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 confidenceWorkTime on-prem allows unauthenticated users to reset the database configuration via a specific HTTP request without any authorization check. An attacker can modify database connection settings without credentials, potentially disrupting service or exposing data.
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<= 11.8.8CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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.
-
Confirm WorkTime installation and versionLocate the WorkTime application installation directory and check the version file or application metadata. Common locations include /opt/worktime, C:\Program Files\WorkTime, or the application root directory. Look for a version.txt, about screen, or check the application banner on startup.Affected if The installed version of Nestersoft Worktime is 11.8.8 or lower.
-
Identify database configuration endpoint exposureReview web server configuration files (such as Apache, Nginx, or embedded server config) and application routing configuration to locate the database configuration REST endpoints. Check for any endpoints related to dbconfig, database, or settings that handle database connection parameters.Affected if The database configuration endpoint is accessible via HTTP/HTTPS without requiring authentication.
-
Verify authentication requirement on configuration routesExamine the application source code or middleware configuration for the database configuration endpoints. Look for authentication decorators, session validation, or authorization checks that should enforce credentials before allowing configuration modifications.Affected if The database configuration endpoint lacks authentication or authorization middleware, allowing unauthenticated requests to reach the configuration logic.
-
Test for unauthenticated configuration modificationUsing a tool like curl or Burp Suite, send a POST or PUT request to the suspected database configuration endpoint without providing any credentials, session cookie, or authorization header. Observe whether the request is accepted or rejected.Affected if The server accepts unauthenticated requests to modify database configuration settings and returns a success response.
You are affected if WorkTime version 11.8.8 or lower is installed and the database configuration endpoint is accessible without any authentication or authorization.
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 dataImplement authentication and role-based authorization checks for all database configuration endpoints. Require admin-level authentication before allowing any configuration modifications.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-15563 — 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-15563 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