CVE-2025-41099
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 · uneditedInsecure Direct Object Reference (IDOR) vulnerability in BOLD Workplanner in versions prior to 2.5.25 (4935b438f9b), consisting of a lack of adequate validation of user input, allowing an authenticated user to access to the list of permissions using unauthorised internal identifiers.
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 confidenceThis is an IDOR vulnerability in BOLD Workplanner where the application fails to properly validate user input when accessing permission lists. An authenticated user can access permission data using unauthorized internal identifiers, allowing unauthorized access to sensitive authorization information.
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< 2.5.25CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Identify installed BOLD Workplanner versionLocate the BOLD Workplanner application installation and retrieve the current version number. This is typically available in the application administrative interface under 'About' or 'System Information', or via the software's built-in version check mechanism.Affected if The installed version is lower than 2.5.25 (e.g., 2.5.24, 2.5.20, etc.)
-
Verify access to permission list endpointsUsing an authenticated user account with standard permissions, attempt to access the permission list functionality within the application. Observe whether the application allows retrieval of permission data by supplying internal identifiers (such as record IDs or permission IDs) that were not explicitly assigned to the current user.Affected if The application returns permission data for identifiers that the current user should not have access to, indicating the IDOR vulnerability is present
-
Check for unauthorized permission data exposureAs an authenticated user with limited or no administrative privileges, attempt to access permission lists or authorization data belonging to other users or roles by manipulating identifier parameters in API requests or application URLs.Affected if The system returns sensitive authorization information (permission lists, role assignments, access controls) for other users or entities without proper authorization validation
-
Review application logs for permission access anomaliesExamine BOLD Workplanner application and server logs for patterns where standard users accessed permission-related endpoints or data that should require elevated privileges.Affected if Logs show authenticated users successfully accessing permission data outside their authorized scope, confirming the IDOR vulnerability is exploitable in the environment
A user is affected if their BOLD Workplanner installation is version 2.5.24 or earlier and the application exposes permission list data to unauthorized authenticated users through direct object reference vulnerabilities.
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 · scoped2.5.25
Upgrade to BOLD Workplanner version 2.5.25 (4935b438f9b) or later, which includes proper validation of user input for permission list access.
2.5.25
- Identify the current installed version of Bold Workplanner by checking the application settings or about page
- Consult the official Bold Workplanner release notes or changelog for version 2.5.25 to understand the changes
- Create a complete backup of the current Bold Workplanner installation including database and configuration files
- Upgrade Bold Workplanner to version 2.5.25 (or latest version after 2.5.25) following the vendor's standard upgrade procedure
- After upgrade, verify that the IDOR vulnerability is resolved by confirming the permission list now requires proper authorization
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41099 — 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-41099 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