CVE-2024-2150
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 · uneditedA vulnerability, which was classified as critical, has been found in SourceCodester Insurance Management System 1.0. This issue affects some unknown processing. The manipulation of the argument page leads to file inclusion. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-255503.
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 confidenceSourceCodester Insurance Management System 1.0 contains a file inclusion vulnerability in the page parameter. An attacker can manipulate this parameter to include arbitrary files from the server file system, potentially exposing sensitive configuration files, credentials, or system files. This is likely a Local File Inclusion (LFI) vulnerability exploitable remotely.
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= 1.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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.
-
Confirm the application versionLocate and identify the installed version of Munyweki Insurance Management System (version 1.0). Check any about page, README file, or system information page within the application.Affected if The installed version is Munyweki Insurance Management System 1.0
-
Identify if the page parameter is in useExamine the application's URL structure to determine if a 'page' parameter is used for navigation or content loading (e.g., index.php?page=somepage).Affected if The application uses a 'page' parameter in its URL routing
-
Verify PHP runtime environmentDetermine if the application server is running PHP, since the vulnerability is in a PHP-based application.Affected if The application is running on a PHP backend
-
Check if the page parameter accepts file pathsObserve whether the page parameter allows direct file path input without strict validation by examining how the application processes this parameter.Affected if The page parameter accepts arbitrary input without validation or sanitization
-
Inspect server-side page handling codeReview the server-side script that processes the page parameter to see if it performs include(), require(), include_once(), or require_once() on the parameter value.Affected if The page parameter is directly used in include/require statements without validation
A user is affected if they are running Munyweki Insurance Management System version 1.0 and the application exposes a page parameter that can be manipulated to include arbitrary server files.
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 strict input validation with an allowlist for permitted page values, use basename() and realpath() to normalize file paths, disable allow_url_include in PHP configurations, and ensure proper directory isolation to prevent path traversal.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2150 — 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-2024-2150 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