dbcve.org
Question Paper GeneratorApplication · Carmelo

CVE-2025-13583

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-24
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 weakness has been identified in code-projects Question Paper Generator 1.0. This affects an unknown part of the file /signupscript.php of the component POST Parameter Handler. Executing manipulation of the argument Fname can lead to sql injection. The attack can be executed remotely. The exploit has been made available to the public and could be exploited.

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 · moderate confidence

SQL injection vulnerability in the Fname POST parameter of /signupscript.php in code-projects Question Paper Generator 1.0 allows remote attackers to manipulate database queries by injecting malicious SQL code through the unsanitized user input.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements in signupscript.php for the Fname parameter, implement strict input validation and sanitization, and consider deploying a WAF as a temporary compensating control until the code fix is deployed.

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
Question Paper GeneratorApplication
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. Confirm the Question Paper Generator 1.0 is installed
    Locate the web application directory and identify if signupscript.php exists in the web root or application directory. Check for files named 'signupscript.php' or directories containing 'Question Paper Generator' or similar naming.
    Affected if The application directory contains signupscript.php and is identified as Question Paper Generator version 1.0
  2. Verify the signup form endpoint is accessible
    Check if the signup form that submits to /signupscript.php is reachable via HTTP. Look for a signup page (often sign up or register) in the application's routing that posts to this endpoint.
    Affected if The signup form is publicly or internally accessible and submits data to signupscript.php via POST method
  3. Inspect signupscript.php for SQL query handling of Fname
    Open signupscript.php in a text editor and locate the code handling the Fname POST parameter. Search for lines where $_POST['Fname'] or similar is used directly in SQL queries without prepared statements, parameter binding, or escaping functions.
    Affected if The Fname parameter is directly concatenated into SQL queries without sanitization, prepared statements, or parameterized queries
  4. Check if database queries use prepared statements
    Review the PHP code in signupscript.php for use of mysqli_prepare, PDO::prepare, or similar parameterized query functions when handling the Fname input. Look for absence of these patterns.
    Affected if SQL queries involving Fname do NOT use mysqli_prepare, PDO::prepare, or equivalent prepared statement methods
  5. Confirm the application is using a vulnerable PHP/MySQL setup
    Verify the backend uses MySQL or MariaDB and the PHP version supports standard database extensions. The vulnerability requires the application to execute dynamic SQL against a MySQL-compatible database.
    Affected if The backend database is MySQL or MariaDB and the application executes the unsanitized Fname parameter in SQL queries

If signupscript.php exists, the signup functionality is accessible, and the Fname parameter is used directly in SQL queries without prepared statements or input sanitization, the environment is vulnerable to CVE-2025-13583.

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

Replace dynamic SQL queries with parameterized queries/prepared statements in signupscript.php for the Fname parameter, implement strict input validation and sanitization, and consider deploying a WAF as a temporary compensating control until the code fix is deployed.

Fix this in Question Paper Generator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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