Description

A weakness has been identified in code-projects Login Registration System 1.0. This affects an unknown function of the file /loginsystem/database/login_registration_system.sql of the component SQL Database Backup Handler. This manipulation causes files or directories accessible. The attack may be initiated remotely. The exploit has been made available to the public and could be used for attacks.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "5.3",
  "pubDate": "2026-08-20T02:16:21.753Z",
  "pubdate": "2026-08-20T02:16:21.753Z",
  "executiveSummary": "A security vulnerability has been identified within the Login Registration System 1.0, specifically affecting the SQL Database Backup Handler component.\nThe vulnerability resides in the file /loginsystem/database/login_registration_system.sql, where improper access controls or misconfigured storage handling leads to an unauthorized files or directories accessible issue.\nThis flaw allows remote attackers to bypass security restrictions and directly access sensitive database backup artifacts without prior authentication.\nSuccessful exploitation of this vulnerability can result in the exposure of critical system data, including user credentials and application state information stored within the SQL database dump.\nThe risk implications are high, as publicly available exploits targeting this vulnerability lower the barrier to entry for malicious actors.\nNo special attacker capabilities or elevated privileges are required to initiate the attack vector over the network, making remediation imperative for securing affected deployments of the Login Registration System product.",
  "technicalDetails": "The vulnerability is classified under an improper access control weakness affecting the SQL Database Backup Handler component of Login Registration System 1.0.\nThe root cause stems from placing sensitive database artifacts, specifically the file /loginsystem/database/login_registration_system.sql, within a web-accessible directory without enforcing proper authorization checks or access restriction directives.\nBecause the file resides in a publicly reachable path, it is exposed to direct HTTP requests over the network.\nThe attack flow begins when an unauthenticated remote attacker sends a standard HTTP GET request directly to the URI corresponding to the database backup file.\nDue to the absence of authentication requirements and privilege checks, the web server processes the request and serves the raw SQL file directly to the client.\nThe payload behavior involves the direct retrieval and download of the complete database structure and contents, which typically contains sensitive operational data, table schemas, and user credential hashes.\nPost-exploitation impact includes credential harvesting for lateral movement or privilege escalation within the application, as well as the potential exposure of personally identifiable information (PII) stored in the database.\nThe affected version is strictly version 1.0 of the Login Registration System, and the vulnerability requires network exposure of the target web root containing the default or unprotected backup file path."
}