dbcve.org
60indexpageApplication · 60indexpage Project

CVE-2024-0946

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-26
Fix available
A fix is available. Upgrade to 1.8.5 or later.
See remediation →
100/100
Remediation priority · Urgent
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 classified as critical was found in 60IndexPage up to 1.8.5. This vulnerability affects unknown code of the file /apply/index.php of the component Parameter Handler. The manipulation of the argument url leads to server-side request forgery. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. VDB-252190 is the identifier assigned to this vulnerability. NOTE: 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 confidence

A critical SSRF vulnerability exists in 60IndexPage versions up to 1.8.5 in the /apply/index.php file's Parameter Handler component. The 'url' parameter is not properly validated, allowing an attacker to make the server perform arbitrary requests to internal or external resources.

MitigationImplement strict input validation and allow-listing for the url parameter to ensure only permitted domains/IPs are reachable. Consider using a whitelist approach and disabling redirect following.

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
60indexpageApplication
Affected:< 1.8.5

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 60IndexPage is installed
    Locate the 60IndexPage application in your web directory. Check for the presence of the main application files, typically found in the web root or a dedicated directory.
    Affected if 60IndexPage software is present on the server
  2. Identify installed version
    Check the application's version file, typically named version.php, README, or changelog in the application root directory. Compare the version number to 1.8.5.
    Affected if The installed version is less than 1.8.5 (any version up to and including 1.8.4)
  3. Verify vulnerable file exists
    Locate the file /apply/index.php within the 60IndexPage installation directory.
    Affected if The file /apply/index.php exists in the application
  4. Check url parameter exposure
    Inspect the /apply/index.php file and search for the 'url' parameter handling code. Verify whether the 'url' parameter is processed without proper validation or allow-listing of reachable domains.
    Affected if The 'url' parameter in /apply/index.php accepts user input without validation or allow-list filtering

The environment is affected if 60IndexPage version is below 1.8.5 and the /apply/index.php file with unvalidated 'url' parameter is accessible and in use.

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
Upgrade available Upgrade to 1.8.5 or later
Fixed in 1.8.5
Interim mitigation

Implement strict input validation and allow-listing for the url parameter to ensure only permitted domains/IPs are reachable. Consider using a whitelist approach and disabling redirect following.

Recommended fix Moderate confidence

60indexpage version 1.8.5 or later

  1. 1. Back up the current 60indexpage installation and database before making any changes.
  2. 2. Download the latest version of 60indexpage (version 1.8.5 or later from the official source).
  3. 3. Replace the existing application files with the new version, preserving any custom configuration files.
  4. 4. Verify the /apply/index.php file has been updated to the fixed version.
  5. 5. Test that the application functions correctly after the upgrade.
  6. 6. Monitor logs for any SSRF attempt indicators targeting the url parameter.
Caveat Review custom configurations and templates after upgrade as they may need adjustment for compatibility

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

Fix this in 60indexpage 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 the upgrade done

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-2024-0946 — 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-2024-0946 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