CVE-2025-60190
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Hinnerk Altenburg Immocaster WordPress Plugin immocaster allows PHP Local File Inclusion.This issue affects Immocaster WordPress Plugin: from n/a through <= 1.3.6.
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 confidenceThe Immocaster WordPress plugin versions up to 1.3.6 contain a Local File Inclusion (LFI) vulnerability due to improper control of filenames in PHP include/require statements. An attacker could potentially exploit this by manipulating file path parameters to read sensitive files from the local filesystem, leading to information disclosure or code execution in certain contexts.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
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 Immocaster plugin installationCheck if the Immocaster plugin directory exists in your WordPress installation at /wp-content/plugins/immocaster/ or similar pathAffected if The plugin directory exists on the server
-
Determine installed plugin versionLocate the version information in the plugin's main PHP file (usually at the top of the file in a comment block) or in the readme.txt file within the plugin directoryAffected if The version cannot be determined or is older than the patched version
-
Identify vulnerable file path parametersSearch the plugin source code for include, require, include_once, or require_once statements that use variables without proper validation (e.g., include($_GET['file']) or similar patterns)Affected if Unvalidated file path parameters are found in the plugin code
-
Test for directory traversal vulnerabilityIf the vulnerable parameter is identified, attempt to access a known local file via directory traversal (e.g., ../../../../wp-config.php) in the affected parameter - only perform this on non-production systems with authorizationAffected if The application allows reading files outside the intended directory through the affected parameter
-
Check access to vulnerable endpointReview server logs or web application firewall logs for requests containing directory traversal patterns (../) targeting the Immocaster plugin endpointsAffected if Exploitation attempts are observed in logs or the endpoint is directly accessible without authentication
Your environment is affected if the Immocaster plugin is installed, contains unvalidated file path parameters in include/require statements, and those parameters are accessible to unauthenticated users.
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 dataUpdate the Immocaster plugin to the latest patched version once available. Until then, disable the plugin or implement a WAF rule to block directory traversal patterns in request parameters.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60190 — 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-60190 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