CVE-2023-1769
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 Grade Point Average GPA Calculator 1.0. Affected is an unknown function of the file index.php. The manipulation of the argument page with the input php://filter/read=convert.base64-encode/resource=grade_table leads to information disclosure. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. VDB-224670 is the identifier 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 confidenceThis vulnerability in SourceCodester GPA Calculator 1.0 allows remote attackers to read arbitrary server files by abusing PHP filter wrappers through the `page` parameter. By supplying `php://filter/read=convert.base64-encode/resource=grade_table`, attackers can retrieve base64-encoded file contents, enabling source code disclosure and potential exposure of sensitive data like credentials.
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 SourceCodester GPA Calculator installationIdentify the application by locating typical GPA Calculator files (index.php, config.php, grade_table files) in your web directory or by checking the application's about/page footer for the product nameAffected if The application is SourceCodester GPA Calculator
-
Verify the version is 1.0Check the version number in source files (often in a config file, readme, or the main PHP files). Look for a version variable or check the application's metadataAffected if The installed version is 1.0
-
Locate the vulnerable include statementSearch the source code for dynamic includes using the 'page' parameter, typically something like: include($_GET['page']), include($_REQUEST['page']), or similar constructs that use the page parameter without sanitizationAffected if The application uses dynamic includes with the page parameter (e.g., include($_GET['page']))
-
Test for PHP filter wrapper acceptanceAttempt a controlled request to your application with a benign php:// filter wrapper in the page parameter, such as: page=php://filter/read=convert.base64-encode/resource=index. Observe if the application attempts to include a PHP stream wrapper instead of rejecting itAffected if The application accepts and processes PHP stream wrappers (php://, phar://) in the page parameter
-
Check input validation on page parameterReview the code handling the page parameter for whitelist validation, allowed file extension checks, or path traversal prevention. Look for functions that validate the page value before using it in an include/require statementAffected if There is NO input validation or whitelist on the page parameter, or the validation can be bypassed
A user is affected if they are running SourceCodester GPA Calculator version 1.0 with a dynamic include using the 'page' parameter and without proper input validation that blocks PHP stream wrappers.
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 on the `page` parameter using a whitelist approach to block path traversal and stream wrapper injection (php://, phar://, etc.). Alternatively, refactor to use a switch/case or array-based page routing instead of dynamic includes.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1769 — 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-1769 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