CVE-2025-41077
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 · uneditedIDOR vulnerability has been found in Viafirma Inbox v4.5.13 that allows any authenticated user without privileges in the application to list all users, access and modify their data. This allows the user's email addresses to be modified and, subsequently, using the password recovery functionality to access the application by impersonating any user, including those with administrative permissions.
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 confidenceIDOR vulnerability in Viafirma Inbox v4.5.13 allows any authenticated user to bypass authorization checks and access/modify data of other users. By modifying a target user's email address through the vulnerable endpoint and then leveraging the password recovery function, an attacker can impersonate any user including administrators.
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< 4.5.27CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 Viafirma Inbox versionCheck the application version through the admin panel, About section, or version API endpoint. Common locations include the system info page, WAR file metadata, or the application's login page footer.Affected if The installed version is lower than 4.5.27
-
Verify user authentication is requiredConfirm that the Viafirma Inbox application requires authentication for all endpoints. Attempt to access API endpoints or pages without providing valid credentials.Affected if The application allows unauthenticated access to user data endpoints
-
Test for object-level authorization on user data endpointsUsing two different authenticated user accounts, attempt to access or modify user-specific resources (such as profile data, email addresses, or user lists) by manipulating object identifiers in API requests. Compare if User A can read/write User B's data.Affected if An authenticated user can access or modify another user's data without proper authorization checks
-
Check if email address changes require additional verificationAttempt to modify an email address through the user profile or settings API without providing the current password or MFA token. Observe if the change is allowed without secondary verification.Affected if Email address changes are permitted without requiring current password or MFA verification
-
Review application logs for IDOR indicatorsExamine application logs for access patterns where user IDs or object references are being accessed by unauthorized users. Look for sequential or enumerated access to user records.Affected if Logs show authenticated users accessing unusually high numbers of other user records or resources outside their authorized scope
The environment is affected if Viafirma Inbox version is below 4.5.27 and the application allows an authenticated user to access or modify another user's data or email address without proper authorization verification.
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 · scoped4.5.27
Implement proper authorization checks to verify the authenticated user has appropriate privileges before allowing access to user listing, viewing, or modification endpoints. Add role-based access control validation to ensure users can only modify their own data.
4.5.27 or later
- 1. Back up the current Viafirma Inbox installation and database before proceeding with the upgrade.
- 2. Download Viafirma Inbox version 4.5.27 or later from the official vendor distribution channel.
- 3. Stop the Viafirma Inbox service to ensure no active sessions during upgrade.
- 4. Install the updated version (4.5.27+) following the vendor's standard upgrade procedure.
- 5. Verify the installation completed successfully and the service starts without errors.
- 6. Test that the IDOR vulnerability is mitigated by attempting to access another user's data with a low-privilege account (this should now be denied).
- 7. Restart the application and confirm all services are running correctly.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.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,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41077 — 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-41077 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