dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-10317

MEDIUM · 5.1 CVSS v4.0 Published 2025-10-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Quick.Cart is vulnerable to Cross-Site Request Forgery in product creation functionality. Malicious attacker can craft special website, which when visited by the admin, will automatically send a POST request creating a malicious product with content defined by the attacker. This software does not implement any protection against this type of attack. All forms available in this software are potentially vulnerable. The vendor was notified early about this vulnerability, but didn't respond with the details of vulnerability or vulnerable version range. Only version 6.7 was tested and confirmed as vulnerable, other versions were not tested and might also be vulnerable.

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

Quick.Cart lacks CSRF protection on its forms, specifically the product creation function. An attacker can craft a malicious webpage that, when visited by an authenticated administrator, automatically submits a POST request to create a product with attacker-controlled content. This occurs because the application does not implement anti-CSRF tokens or any other CSRF mitigation.

MitigationImplement synchronizer token pattern (anti-CSRF tokens) on all state-changing forms including product creation, and validate tokens on the server side. Alternatively, configure SameSite attribute on session cookies.

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
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Quick.Cart installation
    Check for Quick.Cart files in the web root directory (common paths: /admin, /cart, or the main PHP files like index.php, config.php). Look for headers or page content containing 'Quick.Cart' branding.
    Affected if Quick.Cart is present in the environment
  2. Inspect product creation form source
    Navigate to the product creation page in the admin panel (typically /admin/?p=products-form or similar). View the HTML source and search for the <form> tag that submits product data via POST. Examine if any input field with name like 'token', 'csrf', 'anticsrf', or '_token' exists within the form.
    Affected if The product creation form HTML contains no anti-CSRF token input field
  3. Capture and analyze session cookie attributes
    Log into the admin panel, open browser developer tools (F12), go to Application/Storage tab, find the session cookie (often named 'PHPSESSID', 'session', or similar). Inspect the cookie attributes for the SameSite setting.
    Affected if The session cookie does not have SameSite=Strict or SameSite=Lax attribute set
  4. Verify server-side CSRF token validation
    If source code is accessible, examine the product creation handler (likely in a file like products.php, admin.php, or similar). Search for token validation logic: look for references to 'csrf', 'token', 'anticsrf' in $_POST or $_SESSION, and check if validation occurs before processing the product creation request.
    Affected if The server-side code that handles product creation does not validate any CSRF token parameter

If Quick.Cart is present AND the product creation form lacks CSRF tokens AND session cookies lack SameSite attribute AND server-side validation is missing, the environment is vulnerable to CVE-2025-10317.

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

Implement synchronizer token pattern (anti-CSRF tokens) on all state-changing forms including product creation, and validate tokens on the server side. Alternatively, configure SameSite attribute on session cookies.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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