CVE-2026-36387
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 Remote Code Execution vulnerability was found in CODEASTRO Membership Management System v1.0 in /add_members.php. This vulnerability affects the file upload functionality, where improper file sanitization allows attackers to inject malicious files which leads RCE.
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 CODEASTRO Membership Management System v1.0 contains an RCE vulnerability in /add_members.php where the file upload functionality lacks proper sanitization, allowing attackers to upload malicious files that can be executed on the server.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Identify the installed version of CODEASTRO Membership Management SystemCheck your application files or administrative interface for the version number. Compare it to v1.0 as listed in the affected versions.Affected if The installed version is v1.0 of CODEASTRO Membership Management System
-
Verify the add_members.php endpoint existsLocate and inspect the /add_members.php file in your web application directory. Confirm the file is present on the server.Affected if The file /add_members.php exists in the application webroot or is accessible via the web server
-
Confirm file upload functionality is enabledAccess the add_members.php page through the web interface and verify if a file upload form or input field is present and functional.Affected if File upload capability is present and enabled on the add_members.php page
-
Check upload directory configurationExamine the web server and application configuration to locate where uploaded files are stored. Verify if the upload directory is accessible via the web server.Affected if Uploaded files are stored in a directory that is web-accessible and allows script execution
-
Inspect file validation in add_members.phpReview the source code of add_members.php to determine if file type validation uses an allowlist approach and performs server-side MIME type verification.Affected if The code lacks proper file type validation or uses only client-side/blacklist-based validation
Your environment is affected if you are running CODEASTRO Membership Management System v1.0 with the add_members.php file upload feature accessible and configured without strict server-side file validation and with script execution enabled in the upload directory.
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 file type validation using an allowlist, verify file MIME type and extension server-side, rename uploaded files, store uploads outside the webroot, and disable script execution in upload directories.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36387 — 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-2026-36387 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