CVE-2026-10806
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 was found in mjperpinosa stumasy. The affected element is an unknown function of the file application/PHP/objects/updates/add_post.php. Performing a manipulation of the argument up_file_to_post results in unrestricted upload. The attack may be initiated remotely. The exploit has been made public and could be used. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is not available. The project was informed of the problem early through an issue report but has not responded yet.
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 confidenceAn unrestricted file upload vulnerability exists in add_post.php where the up_file_to_post parameter accepts any file type without validation. An attacker can upload malicious executable files (e.g., PHP scripts) leading to potential remote code execution 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
- 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.
-
Locate the add_post.php scriptSearch web root and application directories for the file add_post.php using: find /var/www -name 'add_post.php' 2>/dev/null or dir /s /b C:\inetpub 2>nul (Windows)Affected if The script exists in a publicly accessible web directory
-
Verify the upload parameter existsOpen add_post.php and search for 'up_file_to_post' to confirm the vulnerable parameter is defined in the scriptAffected if The up_file_to_post parameter is present in the code
-
Check for file validation logicInspect the add_post.php code around the up_file_to_post handling for validation functions such as mime_content_type, finfo_file, pathinfo extension checks, or array of allowed extensionsAffected if No MIME type checking, extension whitelist, or magic byte validation is found near the upload handling code
-
Inspect the upload directory configurationLook for the target upload directory path in the code and check if files are stored within or outside the web rootAffected if Uploaded files are stored inside the web root without renaming
-
Test upload functionality if accessibleIf the script is web-accessible, attempt a safe test upload with a non-executable file type (e.g., .txt) and verify it is accepted without rejectionAffected if The script accepts file uploads without validating the file type or extension
A system is affected if add_post.php with the up_file_to_post parameter exists and lacks proper server-side file validation (MIME type, extension whitelist, magic bytes) with uploads stored in a way they can be executed.
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 type allowlisting, store uploads outside the web root, disable script execution in upload directories, and rename uploaded files to prevent direct access.
- 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-10806 — 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-10806 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