dbcve.org
Mobile ShopApplication · Anisha

CVE-2025-7409

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-10
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 was found in code-projects Mobile Shop 1.0 and classified as critical. This issue affects some unknown processing of the file /LoginAsAdmin.php. The manipulation of the argument email leads to sql injection. The attack may 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

SQL injection vulnerability in Mobile Shop 1.0's /LoginAsAdmin.php script allows remote attackers to inject malicious SQL queries via the 'email' parameter. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries, potentially leading to unauthorized access, data exfiltration, or complete database compromise.

MitigationReplace dynamic SQL queries with parameterized queries or prepared statements for all user inputs in the LoginAsAdmin.php file. Validate and sanitize all inputs, and apply principle of least privilege to the database user account used by 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
Mobile ShopApplication
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 the LoginAsAdmin.php file
    Search the web server document root for the file LoginAsAdmin.php (e.g., find /var/www -name 'LoginAsAdmin.php' or search in typical application directories like /admin, /php, or the web root)
    Affected if The file exists in the application directory, indicating the vulnerable component is present
  2. Verify the application version
    Check the application's version information - look for a version file, header, or metadata that indicates the installed version of Anisha Mobile Shop
    Affected if The installed version is 1.0, matching the affected version listed for this CVE
  3. Examine the email parameter handling in LoginAsAdmin.php
    Open LoginAsAdmin.php and inspect the code that handles the 'email' parameter - look for SQL query construction where the email input is directly concatenated into the query string without using prepared statements or parameter binding
    Affected if The code shows the email parameter being inserted directly into an SQL query without sanitization, parameterized queries, or prepared statements (e.g., no mysqli_prepare, PDO::prepare, or similar)
  4. Confirm the application is accessible via web
    Verify the application is deployed and accessible - attempt to access the LoginAsAdmin.php endpoint (e.g., GET request to http://[host]/LoginAsAdmin.php) to confirm the vulnerable script is exposed
    Affected if The LoginAsAdmin.php script is accessible over the network and accepts user input through the email parameter

If Anisha Mobile Shop version 1.0 is installed, the LoginAsAdmin.php file exists, and the email parameter is handled without parameterized queries, the environment is affected by this SQL injection vulnerability.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries or prepared statements for all user inputs in the LoginAsAdmin.php file. Validate and sanitize all inputs, and apply principle of least privilege to the database user account used by the application.

Recommended fix Low confidence
  1. 1. Locate the /LoginAsAdmin.php file in the Mobile Shop 1.0 application
  2. 2. Find the vulnerable SQL query that uses the 'email' parameter without proper sanitization
  3. 3. Replace string concatenation or direct variable insertion in the SQL query with prepared statements (PDO prepared statements or mysqli_prepare)
  4. 4. Use parameterized queries: instead of "SELECT * FROM users WHERE email='$email'", use "SELECT * FROM users WHERE email=?" with bind parameters
  5. 5. Validate and sanitize all user inputs before using them in database queries
  6. 6. Apply the principle of least privilege to the database user account used by the application
  7. 7. Test the login functionality to ensure the fix works correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mobile Shop Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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