dbcve.org
Land Record SystemApplication · Phpgurukul

CVE-2024-13083

MEDIUM · 5.4 CVSS v3.1 Published 2024-12-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 problematic has been found in PHPGurukul Land Record System 1.0. Affected is an unknown function of the file /admin/admin-profile.php. The manipulation of the argument Admin Name leads to cross site scripting. It is possible to launch the attack 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

A stored cross-site scripting (XSS) vulnerability exists in PHPGurukul Land Record System 1.0 within the /admin/admin-profile.php page. The 'Admin Name' parameter is not properly sanitized before storage and display, allowing injection of malicious JavaScript that executes when administrators view the profile.

MitigationImplement proper input validation and output encoding for the Admin Name parameter. Use context-appropriate escaping when rendering the admin name in HTML output.

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

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

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 PHPGurukul Land Record System is installed
    Look for the application in your web server's document root. Check for directories/files such as /land-record/ or common paths where this application may have been deployed. Also check for the presence of index.php or landing pages specific to this system.
    Affected if The application is not present in your environment, you are not affected.
  2. Verify the installed version is 1.0
    Check the version file, readme, or any version declaration within the application source code. The affected version is specifically 1.0.
    Affected if Your installed version is 1.0 and the vulnerability applies.
  3. Locate and inspect admin-profile.php
    Navigate to the /admin/ directory in your web server and verify the presence of admin-profile.php. This file handles admin profile management.
    Affected if The file admin-profile.php does not exist in your installation, you are likely not affected or have a different version.
  4. Verify admin access to the profile page
    Attempt to access /admin/admin-profile.php with valid administrator credentials. The vulnerability requires an authenticated admin session to inject the malicious payload.
    Affected if You cannot access the admin panel or admin-profile.php, the flaw cannot be exploited.
  5. Inspect Admin Name parameter handling
    Review the source code of admin-profile.php. Look for how the Admin Name field is processed - check if the code reads from the database and displays it without sanitization or output encoding. Search for SQL queries handling admin name and HTML output statements rendering this value.
    Affected if The code stores and displays the Admin Name without proper sanitization (no htmlspecialchars, no input validation, no output encoding), you are affected by this stored XSS.

You are affected if PHPGurukul Land Record System version 1.0 is installed, you have admin access, and the Admin Name parameter in admin-profile.php is rendered without sanitization or output encoding.

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 proper input validation and output encoding for the Admin Name parameter. Use context-appropriate escaping when rendering the admin name in HTML output.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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