CVE-2025-28009
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 SQL Injection vulnerability exists in the `u` parameter of the progress-body-weight.php endpoint of Dietiqa App v1.0.20.
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 confidenceA SQL Injection vulnerability exists in the 'u' parameter of the progress-body-weight.php endpoint in Dietiqa App v1.0.20. An attacker can inject malicious SQL statements through this parameter to manipulate database queries, potentially extracting sensitive data, modifying records, or gaining unauthorized access to the application.
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.0.20CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Dietiqa App versionLocate the application version indicator in your installation (typically in an about page, config file, or application metadata). Compare the installed version to 1.0.20.Affected if The installed version is exactly 1.0.20
-
Confirm progress-body-weight.php existsSearch for the file progress-body-weight.php in the web application directory structure.Affected if The file exists in the deployed application
-
Inspect 'u' parameter handlingOpen progress-body-weight.php and locate the code that processes the 'u' parameter. Search for where this parameter is used in SQL queries.Affected if The 'u' parameter is directly concatenated into SQL queries without using parameterized queries, prepared statements, or input sanitization
-
Check database query implementationReview all database queries in progress-body-weight.php that involve the 'u' parameter. Verify whether they use mysqli_prepare, PDO::prepare, or similar parameterized query mechanisms.Affected if Database queries involving the 'u' parameter do not use prepared statements or parameterized queries
-
Test for vulnerability presenceIf the application is accessible, send a request to progress-body-weight.php with a test value in the 'u' parameter (e.g., u=test' OR '1'='1) and observe whether SQL error messages are returned or the query behavior changes unexpectedly.Affected if The application returns SQL syntax errors or exhibits unexpected behavior based on injected input
You are affected if the Dietiqa App version is 1.0.20, the progress-body-weight.php endpoint exists, and the 'u' parameter is used directly in SQL queries without parameterized statements.
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 parameterized queries or prepared statements for all database interactions involving user input. Apply input validation and sanitization as an additional defense layer. Update to a patched version if available.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-28009 — 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-2025-28009 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