CVE-2023-7058
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 found in SourceCodester Simple Student Attendance System 1.0. It has been declared as critical. Affected by this vulnerability is an unknown functionality. The manipulation of the argument page leads to path traversal: '../filedir'. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-248749 was assigned to this vulnerability.
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 confidenceA path traversal vulnerability in SourceCodester Simple Student Attendance System 1.0 allows remote attackers to access arbitrary files outside the web root by manipulating the 'page' parameter with '../' sequences. The lack of input sanitization on this parameter enables directory traversal attacks that could lead to sensitive file disclosure or further compromise.
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.
-
Confirm application identityIdentify if the SourceCodester Simple Student Attendance System is installed in your environment by checking for its distinctive login page, attendance management features, or source code files typically found in the web root directory.Affected if The application is present and matches version 1.0 exactly.
-
Verify the exact version numberLocate and examine version information within the application source code, such as in header files, configuration files, or the main index.php where the version may be hardcoded or defined as a constant.Affected if The installed version is exactly 1.0, as this is the sole affected version.
-
Check for web server exposureDetermine if the application is accessible over HTTP/HTTPS by accessing the main entry point through a web browser or curl request to see if the 'page' parameter is accepted in the URL query string.Affected if The application is web-facing and accepts the 'page' parameter in URLs.
-
Inspect input validation on the page parameterExamine the server-side code that handles the 'page' parameter, typically found in the main PHP file that includes or requires other files based on this parameter, and verify whether path traversal sequences like '../' are being filtered or blocked.Affected if The page parameter accepts '../' sequences without sanitization or validation, allowing directory traversal.
You are affected if the Simple Student Attendance System version 1.0 is web-accessible and the 'page' parameter lacks input validation against path traversal sequences.
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 for the page parameter using allowlists, normalize and sanitize all file paths, and consider restructuring file inclusion logic to avoid direct user-controlled paths. Apply web server restrictions to limit accessible directories.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-7058 — 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-7058 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