CVE-2023-25791
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 · uneditedMissing Authorization vulnerability in Cadus Pro Fontiran allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Fontiran: from n/a through 2.1.
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 · moderate confidenceMissing authorization vulnerability in Cadus Pro Fontiran allows attackers to exploit incorrectly configured access control security levels, potentially bypassing authentication mechanisms to access restricted functionality or resources that should require proper authorization validation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
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 Fontiran installationLocate the Cadus Pro Fontiran application in your environment. Check for directories or files named 'Fontiran', 'fontiran', or similar variations. Also check your web server configuration for any Fontiran-related virtual hosts or application mappings.Affected if Fontiran is present in the environment and has incorrect access control configuration.
-
Review access control security level settingsExamine Fontiran's configuration files for security level parameters. Look for settings related to access control, authentication requirements, or permission levels. Check configuration files such as config.php, settings.xml, web.config, or any .env files in the Fontiran directory.Affected if Security level is set to a value that does not enforce proper authorization validation.
-
Inspect authorization checks on sensitive endpointsReview the application's source code or examine HTTP responses when accessing restricted URLs. Test accessing administrative functions, user data endpoints, or protected resources without providing credentials or with low-privilege credentials.Affected if Restricted resources are accessible without proper authorization validation being enforced.
-
Check for misconfigured access control listsLook for ACL files, .htaccess rules, or similar access control definitions within the Fontiran installation. Verify if security rules are properly defined and not set to overly permissive states such as 'allow all' or 'bypass'.Affected if Access control rules are configured to bypass authentication or grant unrestricted access.
You are affected if Cadus Pro Fontiran is installed and its access control security levels are configured to allow unauthorized access to restricted functionality.
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 proper authorization checks throughout the Fontiran application and correct the misconfigured access control security levels. Ensure all sensitive endpoints and functions validate user permissions before granting access.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25791 — 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-2023-25791 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