CVE-2013-10066
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 · uneditedAn unauthenticated arbitrary file upload vulnerability exists in Kordil EDMS v2.2.60rc3. The application exposes an upload endpoint (users_add.php) that allows attackers to upload files to the /userpictures/ directory without authentication. This flaw enables remote code execution by uploading a PHP payload and invoking it via a direct HTTP request.
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 confidenceUnauthenticated arbitrary file upload vulnerability in Kordil EDMS v2.2.60rc3. The users_add.php endpoint allows remote attackers to upload arbitrary files to the /userpictures/ directory without authentication, enabling remote code execution through direct HTTP requests to uploaded PHP payloads.
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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 Kordil EDMS installationSearch the web server document root for Kordil EDMS files such as login.php, index.php, or configuration files that reference 'Kordil EDMS'. If the application is found, note the installation directory.Affected if Kordil EDMS is present on the server
-
Identify installed versionLocate and inspect version files, about.php, or any file containing version metadata within the Kordil EDMS installation. Compare the discovered version against v2.2.60rc3.Affected if The installed version is v2.2.60rc3 or falls within the v2.2.60 release candidate line
-
Verify users_add.php existsCheck if the file users_add.php exists in the web-accessible directory, typically under the application root or an admin/includes folder.Affected if users_add.php is present in the web directory structure
-
Check userpictures directory accessibilityInspect the /userpictures/ directory under the web root. Verify if it exists and is writable by the web server process.Affected if The /userpictures/ directory exists and is writable
-
Confirm authentication is not enforced on upload endpointReview the source code of users_add.php to determine if authentication, session validation, or access control checks are performed before allowing file uploads. Also test by attempting a direct HTTP POST request to users_add.php without providing any session credentials.Affected if users_add.php allows file upload requests without requiring valid authentication or session tokens
A user is affected if Kordil EDMS v2.2.60rc3 is installed with the users_add.php endpoint accessible and the /userpictures/ directory writable without authentication enforcement.
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 dataImmediately restrict access to the users_add.php endpoint by implementing authentication and session validation; add strict allowlist-based file type validation and disable script execution in the /userpictures/ directory.
- 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-2013-10066 — 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-2013-10066 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