CVE-2023-0943
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, which was classified as problematic, has been found in SourceCodester Best POS Management System 1.0. This issue affects the function save_settings of the file index.php?page=site_settings of the component Image Handler. The manipulation of the argument img with the input ../../shell.php leads to unrestricted upload. The attack may be initiated remotely. The associated identifier of this vulnerability is VDB-221591.
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 confidencePath traversal leading to unrestricted file upload in SourceCodester Best POS Management System 1.0. The save_settings function in the site_settings page fails to validate the img parameter, allowing attackers to use '../../' sequences to write malicious PHP files to arbitrary server locations, potentially achieving 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 the installed application versionLocate and inspect the application files or admin panel to confirm the version number. Look for version information in the application header, footer, about page, or configuration files.Affected if The installed version is Best POS Management System 1.0 (exact match)
-
Confirm the site_settings functionality existsAccess the site_settings page in the application admin interface. This is typically found in the administration or settings section of the POS system.Affected if The site_settings page is present and accessible without additional authentication beyond normal admin access
-
Check for unexpected PHP files in web-accessible directoriesSearch the web server document root and subdirectories for PHP files that were not part of the original installation. Look in non-standard locations such as the root directory, /images/, /uploads/, /assets/, or other writable directories.Affected if PHP files exist in locations outside the expected application structure, especially if they contain suspicious code or were created around the time of potential exploitation
-
Inspect web server logs for path traversal patternsReview web server access and error logs for requests to the save_settings function that contain '../../' sequences in the img parameter. Check both application and web server logs.Affected if Log entries show requests with path traversal sequences targeting the img parameter in save_settings
-
Verify upload directory restrictionsExamine the web server and application configuration to determine if upload directories are properly restricted from executing uploaded files. Check if uploaded files can be accessed directly via URL.Affected if Upload directories allow PHP file execution or are located within web-accessible paths without restrictions
The environment is affected if running Best POS Management System version 1.0 and the site_settings page is accessible, as the vulnerability allows path traversal in the img parameter of the save_settings function.
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 input validation to reject path traversal sequences in file upload parameters, restrict upload directories to non-executable locations, and validate file types/magic bytes before allowing uploads.
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0943 — 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-2023-0943 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