CVE-2024-6950
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 Prain up to 1.3.0. Affected by this issue is some unknown functionality of the file /?import of the component HTTP POST Request Handler. The manipulation of the argument file leads to code injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-272072.
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 confidenceA code injection vulnerability in Prain CMS up to 1.3.0 allows remote attackers to inject malicious code via the 'file' parameter in HTTP POST requests to the /?import endpoint (HTTP POST Request Handler). The lack of proper input validation on the file argument enables arbitrary code execution.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 Prain CMS installationSearch web server directories for Prain CMS files (look for directories named 'prain', 'cms', or files with 'prain' in the name). Check common web root locations for Prain CMS index or configuration files.Affected if Prain CMS is present in the environment
-
Determine installed Prain CMS versionLocate and read the version file or footer in Prain CMS installation. Common locations include version.php, config files, or the main index page source. Compare the version number to 1.3.0.Affected if Installed version is 1.3.0 or lower (any version up to and including 1.3.0)
-
Verify /?import endpoint accessibilitySend an HTTP GET or POST request to the /?import endpoint on the server. Use a tool like curl: curl -X POST http://TARGET/?importAffected if The endpoint responds and accepts requests (endpoint exists and is reachable)
-
Check import functionality access controlsReview the application's authentication configuration or test the /?import endpoint without credentials to determine if authentication is required.Affected if The /?import endpoint is accessible without authentication (no login or token required)
-
Inspect server logs for exploitation attemptsReview web server access logs for POST requests to /?import containing suspicious file parameter values or code injection patterns.Affected if Log entries show POST requests to /?import with unusual file parameter content
A user is affected if Prain CMS version 1.3.0 or lower is installed AND the /?import endpoint is exposed and accessible, allowing unauthenticated code injection via the file parameter.
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 dataRestrict or disable the vulnerable /?import endpoint until a patch is available; implement strict input validation and sanitization on the file parameter; consider adding authentication requirements for import functionality.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6950 — 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-6950 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