CVE-2019-15091
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 · uneditedfilemgr.php in Artica Integria IMS 5.0.86 allows index.php?sec=wiki&sec2=operation/wiki/wiki&action=upload arbitrary file upload.
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 confidenceThe filemgr.php component in Artica Integria IMS 5.0.86 contains an arbitrary file upload vulnerability via the wiki upload action at index.php. The upload function lacks proper validation of file types, contents, or filename sanitization, allowing attackers to upload malicious files directly to the web server.
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= 5.0.86CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/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.
-
Verify Artica Integria IMS versionCheck the installed version of Artica Integria IMS by accessing the application login page or checking system files/headers. Compare against version 5.0.86 specifically.Affected if The installed version is exactly 5.0.86 (the only affected version per the CVE)
-
Locate filemgr.php componentSearch the web root directory for the file filemgr.php. Common paths may include /var/www/html/, /www/, or the application's document root. Use command: find /path/to/webroot -name 'filemgr.php'Affected if filemgr.php exists in a web-accessible directory and is readable by the web server user
-
Confirm index.php wiki upload endpointCheck if index.php accepts a 'wiki' upload action. Inspect the application's web accessible paths, typically at /index.php or /pandora_console/index.php for Integria IMS. Test for the upload functionality by examining if the endpoint responds to upload-related parameters.Affected if The index.php endpoint is accessible and processes file upload requests without authentication or with low-privileged user access
-
Check upload directory permissions and locationIdentify where uploaded files are stored by examining the filemgr.php code or testing an upload. Common locations may be within /var/www/html/, /uploads/, or /attachment/ directories.Affected if Uploaded files are stored within the web root in an executable directory (e.g., not outside /var/www/html/)
The environment is affected if Artica Integria IMS version 5.0.86 is installed AND the filemgr.php component with wiki upload functionality is accessible on the web server, allowing unauthenticated or low-privilege attackers to upload executable files to a web-accessible location.
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 server-side file validation including MIME type checking, extension allowlist, filename sanitization, and store uploads outside the web root or in a non-executable directory.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15091 — 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-2019-15091 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