CVE-2023-1790
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, was found in SourceCodester Simple Task Allocation System 1.0. Affected is an unknown function of the file index.php. The manipulation of the argument page leads to information disclosure. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-224724.
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 Simple Task Allocation System 1.0 index.php file contains an information disclosure vulnerability via the 'page' parameter. Attackers can manipulate this parameter to access sensitive files or data that should not be publicly exposed, likely through path traversal or improper input validation. This remote attack vector allows unauthenticated attackers to potentially read configuration files, source code, or other sensitive system information.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Confirm Simple Task Allocation System installationIdentify the web application running on your server and check its version number or banner information. Look for application files or documentation that indicates the software name and version.Affected if The installed application is Simple Task Allocation System version 1.0
-
Locate the vulnerable index.php fileSearch your web root directory for the index.php file that is part of the Simple Task Allocation System application. Verify it handles a 'page' parameter.Affected if The index.php file from Simple Task Allocation System 1.0 exists and is accessible via the web server
-
Verify unauthenticated access is possibleAttempt to access the index.php file without providing any authentication credentials. Determine if the application allows unauthenticated requests to reach the page parameter functionality.Affected if The application allows unauthenticated access to index.php with the page parameter
-
Test page parameter for information disclosureSend HTTP requests to index.php with manipulated 'page' parameter values (such as ../../etc/passwd or other file paths) to determine if the application returns sensitive file contents without proper validation.Affected if The 'page' parameter accepts path traversal input and returns contents of files outside the intended directory
Your environment is affected if you are running Simple Task Allocation System version 1.0 with the index.php file accessible and the 'page' parameter vulnerable to path traversal, allowing unauthenticated users to read sensitive files.
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 and sanitization on the 'page' parameter to restrict access to allowed files only, combined with proper access controls and directory restrictions to prevent unauthorized file access.
- 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-2023-1790 — 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-1790 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