CVE-2024-35351
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 has been discovered in Diño Physics School Assistant version 2.3. This vulnerability impacts unidentified code within the file /classes/SystemSettings.php?f=update_settings. Manipulating the parameter name results in cross-site scripting.
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 confidenceThis is a stored XSS vulnerability in Diño Physics School Assistant v2.3. The vulnerability exists in the /classes/SystemSettings.php?f=update_settings endpoint where the 'name' parameter is not properly sanitized before storage, allowing injection of malicious JavaScript that executes when other users view the affected page.
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= 2.3CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 Dino Physics School Assistant installation and versionLocate the application installation directory and check version files (such as version.php, about.php, or the system info page) for the exact version number 2.3Affected if The installed version is exactly 2.3
-
Verify SystemSettings.php endpoint existsCheck if the file /classes/SystemSettings.php exists in the web application directory and is accessible via HTTPAffected if The file exists and the web server can serve it
-
Check admin access to settings functionalityLog in as an administrator and navigate to the settings page that uses the update_settings function, or attempt to access the /classes/SystemSettings.php?f=update_settings endpointAffected if The settings update functionality is accessible and operational
-
Inspect stored settings for injected scriptsExamine the database table that stores system settings (typically look for a settings or configuration table), specifically the 'name' field or any parameter that maps to the 'name' input in update_settings, for any unexpected HTML, script tags, or JavaScript codeAffected if The 'name' parameter or related settings field contains unsanitized HTML, script tags, or JavaScript payloads such as <script>alert()</script>
A user is affected if they are running Dino Physics School Assistant version 2.3, the SystemSettings.php update_settings endpoint is accessible, and the 'name' parameter in stored settings contains malicious JavaScript code that was not escaped or sanitized.
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 proper input validation and output encoding on the 'name' parameter in the update_settings function. Sanitize user inputs and escape output when displaying the parameter value to prevent script execution.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35351 — 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-2024-35351 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