dbcve.org
Land Record SystemApplication · Phpgurukul

CVE-2025-7757

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-17
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
Public exploit 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
A vulnerability classified as critical was found in PHPGurukul Land Record System 1.0. Affected by this vulnerability is an unknown functionality of the file /edit-property.php. The manipulation of the argument editid leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.

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 PHPGurukul Land Record System 1.0's /edit-property.php file. The editid parameter is not properly sanitized, allowing remote attackers to inject arbitrary SQL queries. This critical flaw (CVSS 9.8) enables complete database compromise including data exfiltration, modification, or deletion.

MitigationImplement prepared statements/parameterized queries for all database operations in edit-property.php, particularly where the editid parameter is used. Apply input validation and escaping as an additional defense layer.

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
Land Record SystemApplication
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. Locate PHPGurukul Land Record System installation
    Search the web root directory for the presence of the Land Record System application files, specifically looking for the edit-property.php file within the application structure.
    Affected if The edit-property.php file exists in the web-accessible directory.
  2. Verify the installed version is 1.0
    Check for version identification files such as README, version.php, or any file containing the version string '1.0'. Compare your installed version against the affected range (= 1.0).
    Affected if The installed version is confirmed as 1.0.
  3. Confirm edit-property.php is accessible via web
    Attempt to access the edit-property.php file through the web server (e.g., http://[target]/edit-property.php) to verify the application endpoint is active and reachable.
    Affected if The file responds to HTTP requests, indicating it is web-accessible.
  4. Identify database interaction with editid parameter
    Examine the source code of edit-property.php and locate where the 'editid' parameter is used in database queries. Look for direct inclusion of this parameter in SQL statements without prepared statements or parameter binding.
    Affected if The code directly incorporates the editid parameter into SQL queries without sanitization or parameterized queries.
  5. Check application database configuration
    Review the database configuration file (typically dbconnect.php, config.php, or similar) to confirm database credentials are accessible to the application, which would allow successful SQL injection exploitation.
    Affected if Database credentials are configured and the application connects to a database using the vulnerable editid parameter.

A user is affected if PHPGurukul Land Record System version 1.0 is installed with the edit-property.php file accessible and the editid parameter used directly in SQL queries without prepared statements.

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 operations in edit-property.php, particularly where the editid parameter is used. Apply input validation and escaping as an additional defense layer.

Fix this in Land Record System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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