dbcve.org
Land Record SystemApplication · Phpgurukul

CVE-2024-13081

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 was found in PHPGurukul Land Record System 1.0. It has been declared as problematic. This vulnerability affects unknown code of the file /admin/contactus.php. The manipulation of the argument Page Description leads to cross site scripting. The attack can be initiated 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 in PHPGurukul Land Record System 1.0 allows remote attackers to inject malicious JavaScript code through the Page Description parameter in /admin/contactus.php. The unsanitized input is stored and executed when viewed by other users.

MitigationImplement proper input validation and output encoding/escaping on the Page Description field in contactus.php to neutralize malicious scripts. Use context-appropriate escaping functions and consider implementing a Content Security Policy (CSP) header.

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. Identify PHPGurukul Land Record System installation
    Search for files or directories associated with PHPGurukul Land Record System on the web server. Check common web directories for a folder containing 'land-record' or 'landrecord' or verify the application banner/footer for the product name.
    Affected if The application is present and appears to be PHPGurukul Land Record System.
  2. Confirm installed version is 1.0
    Locate the version identifier in the application source code, such as in an index file, readme, or configuration file. Compare your installed version against the affected range (= 1.0).
    Affected if The installed version is exactly 1.0.
  3. Verify admin/contactus.php exists
    Check for the presence of the file /admin/contactus.php in the web root directory of the application.
    Affected if The file /admin/contactus.php exists on the server.
  4. Check if admin panel is accessible
    Attempt to access the /admin/ directory or login page to determine if the administrative interface is reachable.
    Affected if The admin panel is accessible without additional authentication or after valid admin credentials are provided.
  5. Inspect database for stored Page Description entries
    Query the database (typically MySQL) for records in the contactus or related table that may contain unsanitized script tags in fields corresponding to Page Description. Use: SELECT * FROM contactus WHERE description LIKE '%<script%' or examine the table structure for fields that store page description data.
    Affected if The database contains records with HTML or script tags in the Page Description field.

A user is affected if they have PHPGurukul Land Record System version 1.0 installed with the /admin/contactus.php file accessible and stored XSS payloads present in the Page Description field of the database.

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/escaping on the Page Description field in contactus.php to neutralize malicious scripts. Use context-appropriate escaping functions and consider implementing a Content Security Policy (CSP) header.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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