dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-41029

CRITICAL · 9.3 CVSS v4.0 Published 2026-04-21
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
SQL injection vulnerability in Zeon Academy Pro by Zeon Global Tech. This vulnerability allows an attacker to retrieve, create, update, and delete databases by sending a POST request using the parameter 'phonenumber' in '/private/continue-upload.php'.

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 Zeon Academy Pro allows remote attackers to execute arbitrary SQL commands via the 'phonenumber' POST parameter in /private/continue-upload.php. The lack of input sanitization or parameterized queries enables complete database compromise, including read, write, update, and delete operations.

MitigationImplement prepared statements/parameterized queries for all database queries, particularly for the phonenumber parameter. Additionally, apply input validation and escaping, and consider deploying a WAF as a defense-in-depth measure.

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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Zeon Academy Pro installation
    Check your web server document root for the Zeon Academy Pro application files. Look for the main installation directory and any version file (commonly version.php, package.json, or a readme file).
    Affected if Zeon Academy Pro is installed and the version cannot be confirmed as patched or is within an unpatched version range.
  2. Verify vulnerable endpoint exists
    Locate the file /private/continue-upload.php in your web server filesystem. This is the script referenced in the CVE as handling the phonenumber parameter.
    Affected if The file /private/continue-upload.php exists in your installation.
  3. Confirm phonenumber parameter acceptance
    Review the source code of /private/continue-upload.php to verify it accepts a POST parameter named 'phonenumber' and uses it in a database query without prepared statements or input sanitization.
    Affected if The code directly incorporates the phonenumber parameter into an SQL query without using parameterized queries, prepared statements, or input escaping.
  4. Check for SQL injection indicators in logs
    Search your web server access logs and database logs for unusual SQL syntax patterns in requests to /private/continue-upload.php. Look for UNION SELECT, OR 1=1, or other SQL injection payloads.
    Affected if Log entries show SQL injection attempts or suspicious SQL syntax in requests to the continue-upload.php endpoint.
  5. Audit database for unauthorized changes
    Review database tables for unexpected modifications, new admin accounts, or data exfiltration indicators. Check for unauthorized INSERT, UPDATE, or DELETE operations around the time of potential exploitation.
    Affected if The database shows unauthorized changes, new suspicious records, or evidence of data access that did not originate from legitimate application logic.

You are affected if Zeon Academy Pro is installed, the /private/continue-upload.php file exists, and the phonenumber parameter is handled without parameterized queries 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

Implement prepared statements/parameterized queries for all database queries, particularly for the phonenumber parameter. Additionally, apply input validation and escaping, and consider deploying a WAF as a defense-in-depth measure.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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