dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-47575

HIGH · 8.5 CVSS v3.1 Published 2025-05-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable 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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in mojoomla School Management allows SQL Injection. This issue affects School Management: from n/a through 92.0.0.

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 mojoomla School Management plugin allows attackers to inject malicious SQL commands through unsanitized user inputs. This could enable unauthorized data access, authentication bypass, or potential data manipulation. The flaw exists in the School Management component affecting versions up to 92.0.0.

MitigationReplace dynamic SQL queries with parameterized queries or prepared statements, implement proper input validation and sanitization on all user-supplied data before database operations, and conduct thorough code review to identify and fix all similar injection points.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L

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. Identify the installed version of the School Management plugin
    Locate the plugin files in your mojoomla installation and check the version number in the plugin configuration file, typically found in the plugin header or version file within the School Management plugin directory
    Affected if The installed version is 92.0.0 or any version below 92.0.0
  2. Confirm the School Management component is active
    Access your mojoomla admin panel and verify that the School Management plugin or module is enabled and running on your site
    Affected if The School Management component is installed and active in the mojoomla environment
  3. Locate SQL query files in the School Management component
    Inspect the source code files within the School Management plugin directory, focusing on files that handle database operations such as those containing SQL query strings or database function calls
    Affected if The component contains PHP files that construct SQL queries dynamically
  4. Inspect user input handling in database operations
    Review the identified SQL query files to trace how user-supplied input (from GET, POST, or request parameters) flows into SQL statements without visible sanitization functions such as parameterized queries, prepared statements, or input validation routines
    Affected if User input parameters are directly concatenated or inserted into SQL queries without escaping, parameter binding, or sanitization functions
  5. Verify the vulnerability exposure point
    Test the identified input fields within the School Management pages by examining the application's response to special characters or SQL syntax in input fields, noting if errors are returned or if the input affects query behavior
    Affected if User-provided input is accepted by the application and directly influences SQL query structure without proper handling

Your environment is affected if the mojoomla School Management plugin is installed at version 92.0.0 or below and contains code where user input flows into SQL queries without parameterized statements or input sanitization.

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 or prepared statements, implement proper input validation and sanitization on all user-supplied data before database operations, and conduct thorough code review to identify and fix all similar injection points.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47575 — 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-2025-47575 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