CVE-2026-10807
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 determined in mjperpinosa stumasy. The impacted element is an unknown function of the file application/PHP/objects/profiles/change_profile_image.php. Executing a manipulation of the argument pr_profile_image can lead to unrestricted upload. The attack may be launched remotely. The exploit has been publicly disclosed and may be utilized. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases. 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 confidenceThe stumasy application contains an unrestricted file upload vulnerability in the change_profile_image.php script. The pr_profile_image parameter accepts user-controlled input without proper validation, allowing attackers to upload arbitrary files including malicious PHP scripts that could lead to remote 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.
-
Locate the change_profile_image.php fileSearch your web server document root for the file 'change_profile_image.php' - typically found in user profile or account management directoriesAffected if The file exists in your web-accessible directory and handles the pr_profile_image parameter
-
Identify the upload form or API endpointInspect the change_profile_image.php code to find where the pr_profile_image parameter is processed and files are receivedAffected if The file directly processes file uploads from the pr_profile_image parameter without validation
-
Check for server-side file validationReview the change_profile_image.php code for MIME type checking, extension whitelist, or file content verification logic before saving uploaded filesAffected if No validation or only client-side validation exists for uploaded files
-
Inspect the upload directoryFind where uploaded files are stored - typically check the configuration or code for the upload path, and verify if it resides within the webrootAffected if Uploads are stored in a web-accessible directory with executable permissions
-
Verify uploaded file execution statusTest uploading a harmless file (like a text file renamed to .php) and attempt to access it via a browser to see if it executes as PHPAffected if Uploaded files are served with executable permissions and can be accessed via URL
You are affected if change_profile_image.php exists in your environment and processes the pr_profile_image parameter without proper server-side file validation, allowing arbitrary file uploads to a web-accessible 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 both file extension allowlists and magic byte verification. Store uploads outside web root, rename files to prevent execution, and apply proper access controls. Additionally, implement size limits and log all upload attempts for monitoring.
- 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-10807 — 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-10807 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