CVE-2025-9847
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 weakness has been identified in ScriptAndTools Real Estate Management System 1.0. Impacted is an unknown function of the file register.php. This manipulation of the argument uimage causes unrestricted upload. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be exploited.
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 confidenceThis is an unrestricted file upload vulnerability in ScriptAndTools Real Estate Management System 1.0. The register.php script accepts a user-provided image upload via the 'uimage' parameter without proper validation, allowing attackers to upload arbitrary executable files (such as PHP scripts) that can be accessed via the web server to 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.
-
Identify if Scriptandtools Real Estate Management System is installedLocate the application webroot and confirm the presence of the Real Estate Management System files, typically found in the web server document root. Check for typical application files like index.php, and review any version identifier in source code or README files.Affected if The application is installed and the version is 1.0
-
Verify register.php exists and is accessibleLocate the register.php file within the application webroot, typically under the /users/ or /register/ directory path. Confirm the file is accessible via HTTP/HTTPS request.Affected if register.php exists and is web-accessible
-
Check if the uimage upload parameter is functionalReview the register.php source code to identify if it processes the 'uimage' parameter for file uploads. Determine if the form accepts file input for user profile images.Affected if The 'uimage' parameter accepts file uploads without restrictions
-
Inspect upload directory location and execution settingsExamine the application's upload directory configuration in register.php or related config files. Identify where uploaded files are stored (within or outside webroot) and whether script execution is disabled in that directory.Affected if Uploaded files are stored within the webroot and script execution is allowed
-
Check for file validation on uploadsReview register.php code to determine if MIME type validation, extension allowlisting, or content-type checking is performed on uploaded files via the 'uimage' parameter.Affected if No MIME type validation, extension allowlisting, or content verification is performed on uploads
A user is affected if they have Scriptandtools Real Estate Management System version 1.0 running with the register.php script accessible and the uimage upload feature enabled without proper file validation.
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 allowlist-based file validation for uploads (MIME type and extension checking), rename uploaded files, store uploads outside the webroot, and disable script execution in upload directories.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9847 — 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-2025-9847 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