Skip to main content
Menu
CVEs

CVE

DevWebister Azon Dominator SQL injection in fetch_products.php via cid parameter

Azon Dominator releases through 2024-06-03 are affected via the cid parameter in fetch_products.php. CVSS rates it High (8.8). The checked facts list no fixed version.

CVE-2024-58402Published Updated Summary written by a model

8.8HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Do first: Workaround: The checked facts give no workaround and no vendor patch. The sources do not say what to limit while no fix exists, so none is named here.

Summary

Azon Dominator releases through 2024-06-03 contain an SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries through the cid parameter in /fetch_products.php. Attackers can send crafted POST requests with boolean-based or time-based blind payloads to extract sensitive database information. Exploitation evidence was first observed by the Shadowserver Foundation on 2024-07-30.

Who should check

Teams and site owners running the DevWebister Azon Dominator affiliate marketing script, release through 2024-06-03.

“Azon Dominator releases through 2024-06-03”

vulncheck.com

cve.now Index

31Pcve.now Index 31 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.8/10CVSS 8.8
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 76 if added to CISA KEV
  • Would score about 71 if CISA's SSVC rates exploitation active
  • Would score about 36 if advisories confirm default setups are exposed

What to do

  • Workaround: The checked facts give no workaround and no vendor patch. The sources do not say what to limit while no fix exists, so none is named here.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2024-58402 (Azon Dominator SQL Injection via fetch_products.php cid parameter), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2024-58402 (entry last updated 2026-11-18):
Affected:
- DevWebister Azon Dominator: through 2024-06-03
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Azon Dominator releases through 2024-06-03 (source: https://www.vulncheck.com/advisories/azon-dominator-sql-injection-via-fetch-products-php-cid-parameter)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2024-58402 is not listed as of cve.now's last read.
This KEV status is for CVE-2024-58402 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.codester.com/items/12775/azon-dominator-affiliate-marketing-script
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/azon-dominator-sqli.yaml
- https://www.vulncheck.com/advisories/azon-dominator-sql-injection-via-fetch-products-php-cid-parameter
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2024-58402
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2024-58402"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • DevWebister Azon Dominator

    through 2024-06-03

Evidence 7

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2024-58402

Is CVE-2024-58402 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The cid parameter in fetch_products.php does not safely handle database queries, so an attacker can change those queries and extract sensitive database information.Source: vulncheck.com

Which versions are affected by CVE-2024-58402?

Azon Dominator: through 2024-06-03.Source: cve.now feed data

Am I affected, and how do I check?

Azon Dominator releases through 2024-06-03 are listed as affected, with no earlier starting version given. To check a copy, compare its release date or version against that date.Source: vulncheck.com

How do I fix CVE-2024-58402?

The checked facts name no fixed version or vendor patch, so no upgrade target can be given from this record. Check the vendor's release notes or advisory for a fix.Source: vulncheck.com

What if there's no patch?

The checked facts give no workaround and no vendor patch. The sources do not say what to limit while no fix exists, so none is named here.Source: vulncheck.com

More CVEs