dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-57805

HIGH · 8.7 CVSS v4.0 Published 2025-08-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/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
The Scratch Channel is a news website. In versions 1 and 1.1, a POST request to the endpoint used to publish articles, can be used to post an article in any category with any date, regardless of who's logged in. This issue has been patched in version 1.2.

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 broken access control vulnerability in the Scratch Channel news website versions 1.0-1.1 allows unauthorized users to publish articles to any category with arbitrary dates via a POST request to the article publishing endpoint, without requiring authentication or proper authorization checks.

MitigationUpgrade to version 1.2 which contains the patch, or implement proper authentication and authorization validation on the article publishing endpoint.

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
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/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. Identify the installed version of Scratch Channel news website
    Check the application source code, version file, or admin panel for the version number. Common locations include a version.php file, package.json, or the admin dashboard About section.
    Affected if The installed version is 1.0 or 1.1 (any version from 1.0 through 1.1 inclusive)
  2. Locate the article publishing endpoint
    Review the application's routing configuration or web server logs for POST requests to paths such as /publish, /article/create, /news/publish, or similar endpoints handling article submission.
    Affected if The article publishing endpoint exists and is accessible via HTTP POST methods
  3. Verify authentication is not required on the publishing endpoint
    Send a test POST request to the publishing endpoint without including any authentication tokens, session cookies, or credentials. Check if the request is processed without authentication failure.
    Affected if The endpoint accepts and processes POST requests without any authentication credentials
  4. Check if category selection lacks authorization controls
    Submit a POST request to the publishing endpoint attempting to publish to different categories (e.g., different category IDs or names) without authorization. Observe if the application accepts arbitrary category assignments.
    Affected if The endpoint allows publishing to any category without verifying user permissions
  5. Verify date fields can be set arbitrarily
    Submit a POST request with custom date parameters (such as publish_date or article_date) set to arbitrary values outside the current date. Confirm if the application accepts and stores these arbitrary dates.
    Affected if The endpoint accepts and stores arbitrary date values without validation

A defender is affected if the Scratch Channel news website version is 1.0 or 1.1 and the article publishing endpoint accepts unauthenticated POST requests that allow arbitrary category assignment and date values.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 1.2 which contains the patch, or implement proper authentication and authorization validation on the article publishing endpoint.

Recommended fix High confidence

Version 1.2

  1. 1. Identify the current version of The Scratch Channel software in use (versions 1 or 1.1 are affected)
  2. 2. Obtain version 1.2 of The Scratch Channel from the official repository
  3. 3. Review the upgrade documentation for version 1.2
  4. 4. Perform a backup of the current application data and configuration
  5. 5. Apply the version 1.2 upgrade following the documented procedure
  6. 6. Verify that the patch resolves the improper input validation by testing article posting with different categories and dates
  7. 7. Confirm proper authentication enforcement is in place for article publishing

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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