dbcve.org
School Erp Pro\+responsiveApplication · Arox

CVE-2024-4824

CRITICAL · 9.8 CVSS v3.1 Published 2024-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Vulnerability in School ERP Pro+Responsive 1.0 that allows SQL injection through the '/SchoolERP/office_admin/' index in the parameters groups_id, examname, classes_id, es_voucherid, es_class, etc. This vulnerability could allow a remote attacker to send a specially crafted SQL query to the server and retrieve all the information stored in the database.

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 confidence

SQL injection vulnerability in School ERP Pro+Responsive 1.0 allows remote attackers to inject arbitrary SQL commands through multiple unsanitized parameters (groups_id, examname, classes_id, es_voucherid, es_class) in the /SchoolERP/office_admin/ endpoint. The lack of input sanitization or parameterized queries enables complete database compromise.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements across all affected parameters, implement strict input validation, and apply the vendor patch if available. Database accounts should run with least privilege.

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
School Erp Pro\+responsiveApplication
Affected:= 1.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Arox School ERP installation
    Locate the application installation directory or check running web services for files named 'SchoolERP' or related components. On Linux check common paths like /var/www/, /home/, or the web server document root. On Windows check IIS wwwroot or Apache htdocs directories.
    Affected if The Arox School ERP Pro+Responsive application is installed on the system.
  2. Verify application version is 1.0
    Check the application version file, about page, or configuration files within the SchoolERP installation directory for a version identifier. Look for version.php, version.txt, or check the main index.php for a version string.
    Affected if The installed version is exactly 1.0, matching the affected release.
  3. Confirm vulnerable endpoint exists
    Check for the existence of the /SchoolERP/office_admin/ directory and its scripts within the web application root. List the files in this directory to confirm the endpoint handlers are present.
    Affected if The /SchoolERP/office_admin/ endpoint directory and its scripts exist in the application.
  4. Check application network exposure
    Determine if the School ERP web application is accessible from network interfaces other than localhost. Review web server configuration, firewall rules, or reverse proxy settings to identify external accessibility.
    Affected if The application is exposed to network or remote access, enabling external attackers to reach the vulnerable endpoint.
  5. Identify if application handles user input via affected parameters
    Review the source code of the office_admin endpoint handlers to confirm they accept and process user input through the parameters: groups_id, examname, classes_id, es_voucherid, and es_class.
    Affected if The application processes user-supplied input through any of the five affected parameters (groups_id, examname, classes_id, es_voucherid, es_class) in the office_admin endpoint.

A system is affected if it runs Arox School ERP Pro+Responsive version 1.0 with the /SchoolERP/office_admin/ endpoint accessible to users and processing input through the affected parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries/prepared statements across all affected parameters, implement strict input validation, and apply the vendor patch if available. Database accounts should run with least privilege.

Fix this in School Erp Pro\+responsive Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-4824 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-4824 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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