dbcve.org
InjectionWeakness · CWE-74

CVE-2026-10260

HIGH · 7.3 CVSS v3.1 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 detected in CodeAstro Online Job Portal 1.0. The impacted element is an unknown function of the file /admin/jobs-admins/delete-jobs.php. Performing a manipulation of the argument ID results in sql injection. It is possible to initiate the attack remotely. The exploit is now 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 CodeAstro Online Job Portal 1.0 allows remote attackers to inject malicious SQL commands via the ID parameter in /admin/jobs-admins/delete-jobs.php. The unsanitized input is directly used in database queries, enabling data exfiltration or manipulation.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements in delete-jobs.php to properly handle the ID parameter, and implement input validation as defense-in-depth.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm CodeAstro Online Job Portal installation
    Search the web root for files containing 'CodeAstro' or 'Online Job Portal' in headers or check for the presence of typical job portal directories like /admin/, /jobs/, /employers/, /jobseekers/. Check version.php or README files if they exist.
    Affected if The application is CodeAstro Online Job Portal version 1.0
  2. Verify vulnerable file exists
    Check if /admin/jobs-admins/delete-jobs.php exists in the web root directory.
    Affected if The file delete-jobs.php exists in the expected path
  3. Check if admin interface is accessible
    Attempt to access the admin login page at /admin/ or /admin/login.php to determine if the admin panel is reachable.
    Affected if The admin panel is accessible without authentication or with valid admin credentials
  4. Inspect SQL query handling in delete-jobs.php
    Open delete-jobs.php and examine how the ID parameter is handled. Look for SQL queries that directly incorporate $_GET['id'] or $_POST['id'] without using prepared statements, parameterized queries, or input sanitization functions like mysqli_real_escape_string or PDO::quote.
    Affected if The ID parameter is used directly in SQL queries without sanitization or parameterization

A user is affected if CodeAstro Online Job Portal 1.0 is installed, the delete-jobs.php file exists, and the ID parameter in that file is used in unsanitized SQL queries.

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 delete-jobs.php to properly handle the ID parameter, and implement input validation as defense-in-depth.

Have this fixed 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-2026-10260 — 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-2026-10260 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