Skip to content

Valtimo backend libraries allows objects in the object-api to be accessed and modified by unauthorized users

High severity GitHub Reviewed Published May 27, 2025 in valtimo-platform/valtimo-backend-libraries • Updated May 30, 2025

Package

maven com.ritense.valtimo:object-management (Maven)

Affected versions

>= 11.0.0.RELEASE, <= 11.3.3.RELEASE
>= 12.0.0.RELEASE, <= 12.12.0.RELEASE

Patched versions

None
maven com.ritense.valtimo:objecten-api (Maven)
>= 11.0.0.RELEASE, <= 11.3.3.RELEASE
>= 12.0.0.RELEASE, <= 12.12.0.RELEASE
None

Description

Impact

All objects for which an object-management configuration exists can be listed, viewed, edited, created or deleted by unauthorised users.

If object-urls are exposed via other channels, the contents of these objects can be viewed independent of object-management configurations.

Attack requirements

The following conditions have to be met in order to perform this attack:

  • A user must be logged in
    • No relevant application roles are required
  • At least one object-type must be configured via object-management
    • The scope of the attack is limited to objects that are configured via object-management.
    • The value of showInDataMenu is irrelevant for this attack

Patches

No patch is available yet

Workarounds

It is possible to override the endpoint security as defined in ObjectenApiHttpSecurityConfigurer and ObjectManagementHttpSecurityConfigurer. Depending on the implementation, this could result in loss of functionality.

References

@theo-ritense theo-ritense published to valtimo-platform/valtimo-backend-libraries May 27, 2025
Published to the GitHub Advisory Database May 28, 2025
Reviewed May 28, 2025
Published by the National Vulnerability Database May 30, 2025
Last updated May 30, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(11th percentile)

Weaknesses

CVE ID

CVE-2025-48881

GHSA ID

GHSA-965r-9cg9-g42p

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.