CVE-2025-15140
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 · uneditedA vulnerability was found in saiftheboss7 onlinemcqexam up to 0e56806132971e49721db3ef01868098c7b42ada. This vulnerability affects unknown code of the file /admin/quesadd.php. Performing manipulation of the argument ans1/ans2 results in sql injection. The attack is possible to be carried out remotely. The exploit has been made public and could be used. This product adopts a rolling release strategy to maintain continuous delivery The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceSQL injection vulnerability in the /admin/quesadd.php file of the onlinemcqexam application. The ans1 and ans2 parameters are not properly sanitized before being used in SQL queries, allowing remote attackers to inject arbitrary SQL code. The exploit is publicly available and the attack can be carried out remotely.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm onlinemcqexam application is installedSearch the web root directory for files or directories containing 'onlinemcqexam' or look for the application's main entry point (typically index.php or similar in the web root)Affected if The application is present in the environment
-
Locate the vulnerable quesadd.php fileSearch the web directory for the file /admin/quesadd.php or check if the path contains 'quesadd.php' in an admin folderAffected if The file /admin/quesadd.php exists in the web application directory
-
Verify application versionCheck any version file, README, or meta information in the application root for the installed version numberAffected if The installed version matches or predates any known vulnerable version of onlinemcqexam
-
Confirm admin interface is accessibleAttempt to access /admin/ or the admin login page through HTTP/HTTPS to verify the administrative interface is exposedAffected if The administrative interface is reachable from the network (not restricted by authentication or network filters)
-
Verify vulnerable parameters exist in the codeExamine the source code of /admin/quesadd.php and locate the ans1 and ans2 parameters to confirm they are used in SQL queries without proper sanitization (parameterized queries or escaping)Affected if The ans1 and ans2 parameters are present and used in dynamic SQL queries without prepared statements or input validation
If the onlinemcqexam application is installed with the /admin/quesadd.php file present and the admin interface is network-accessible, the environment is likely affected by this SQL injection vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace dynamic SQL queries with parameterized queries/prepared statements for the ans1 and ans2 parameters. Apply input validation and use least-privilege database accounts. Consider a WAF as a temporary mitigation while the code fix is being implemented.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-15140 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-15140 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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