CVE-2026-0643
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 flaw has been found in projectworlds House Rental and Property Listing 1.0. Impacted is an unknown function of the file /app/register.php?action=reg of the component Signup. This manipulation of the argument image causes unrestricted upload. Remote exploitation of the attack is possible. The exploit has been published and may be used.
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 House Rental and Property Listing 1.0 application has an unrestricted file upload vulnerability in the signup functionality at /app/register.php?action=reg. The 'image' parameter accepts files without proper validation, allowing attackers to upload malicious files (e.g., PHP web shells) and achieve remote code execution.
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= 1.0CVSS 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.1/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.
-
Locate the application installationSearch for the presence of register.php in the /app/ directory or any web-accessible directory. Common paths: /app/register.php, /register.php, or within a house-rental/ directory.Affected if The file /app/register.php exists on the server.
-
Verify the application versionCheck for version indicators in source files, such as comments in PHP files, version.txt, README files, or any configuration files that may contain the version number. Compare against version 1.0.Affected if The installed version is Projectworlds House Rental And Property Listing 1.0.
-
Confirm the vulnerable endpoint existsAccess or inspect the file /app/register.php and verify the 'action=reg' parameter handling exists. Look for the 'image' parameter in form submissions.Affected if The register.php file contains an 'image' file upload field and processes it without apparent validation.
-
Inspect file upload validation logicExamine the register.php code for file validation functions. Look for checks on file extension, MIME type, content type, or file content headers before moving the uploaded file.Affected if The code lacks or has weak validation - no extension allowlist, no MIME type verification, or no content-type checking before file move operations.
-
Check upload directory configurationIdentify where uploaded files are stored. Look for move_uploaded_file() calls or similar file handling functions in register.php. Determine if uploads are stored inside the web root.Affected if Uploaded files are saved within the web-accessible directory without disabling script execution.
You are affected if the House Rental And Property Listing 1.0 is installed, the /app/register.php endpoint with the 'image' parameter exists, and there is no proper file type validation or secure upload storage configuration.
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 extension allowlists and MIME type checking, validate actual file content/headers, store uploads outside the web root, and disable script execution in upload directories.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0643 — 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-0643 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