CVE-2005-1964
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 · uneditedPHP remote file inclusion vulnerability in utilit.php for Ovidentia Portal allows remote attackers to execute arbitrary PHP code via the babInstallPath parameter.
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 confidenceRemote File Inclusion (RFI) vulnerability in Ovidentia Portal's utilit.php allows attackers to inject arbitrary PHP code through the babInstallPath parameter, enabling remote code execution on the server.
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= fxCVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Locate Ovidentia Portal installationSearch the web server's document root for files or directories containing 'ovidentia', 'cantico', or 'utilit.php'. Common paths include /var/www/, /home/*/public_html/, or C:\inetpub\wwwroot\Affected if Ovidentia Portal software is present on the server
-
Verify utilit.php existsIf Ovidentia is found, check for the presence of the file utilit.php in the installation directory, typically in the root or includes folderAffected if The file utilit.php exists in the Ovidentia installation directory
-
Check PHP allow_url_include settingRun 'php -i' or create a PHP script with 'phpinfo();' to check the PHP configuration. Look for the allow_url_include directive in the outputAffected if allow_url_include is set to On (enabled) in php.ini or PHP configuration
-
Inspect utilit.php for babInstallPath usageOpen utilit.php in a text editor and search for 'babInstallPath' being used in include(), require(), include_once(), or require_once() statements without proper validation such as file_exists() checks or allowlist validationAffected if The babInstallPath parameter is used in include/require statements without sanitization or allowlisting validation
The server is affected if Ovidentia Portal is installed, utilit.php is present, allow_url_include is enabled in PHP, and babInstallPath is used in include/require statements without input validation.
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 dataDisable allow_url_include in PHP configuration and implement strict input validation/allowlisting on the babInstallPath parameter before using it in include/require statements.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-1964 — 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-2005-1964 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