Sc FilecheckerWordPress extension · Sc Filechecker Project
CVE-2024-35743
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 · uneditedImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Siteclean SC filechecker allows Path Traversal, File Manipulation.This issue affects SC filechecker: from n/a through 0.6.
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 confidenceThe Siteclean SC filechecker component contains a path traversal vulnerability (CWE-22) that allows attackers to access files outside the intended directory by manipulating file paths with '../' sequences. This improper input validation on file paths enables unauthorized file manipulation.
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
Sc FilecheckerWordPress extension
<= 0.6CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Sc Filechecker component installationLocate the Siteclean SC filechecker component on your system. Check for files or packages named 'sc filechecker', 'filechecker', or the project directory 'Sc-Filechecker'. Look in application directories, installed plugins, or bundled software folders.Affected if The component is not found on the system, then this CVE does not apply.
-
Identify the installed versionExamine version information for the filechecker component. Check the project metadata file (such as version.py, setup.py, package.json, or a VERSION file), the component's about page, or the main executable's version flag. Compare the found version against the affected range: <= 0.6.Affected if The installed version is 0.6 or lower, the component is vulnerable to path traversal.
-
Verify the file path input feature is accessibleDetermine whether the filechecker component accepts file paths as input for processing. This may be through a web interface, API endpoint, CLI argument, or configuration setting that takes a file path to check. Check if the component exposes functionality where users can specify which files to process or scan.Affected if The file path input feature is exposed and accepts arbitrary paths, the path traversal vulnerability can be exploited.
-
Check for external or untrusted input sourcesIdentify if the file path input can be supplied by external users, remote requests, or untrusted sources rather than only by authenticated administrators locally. Review access controls, network exposure, and input validation on the file path parameter.Affected if External or untrusted users can supply file paths to the component, they can exploit the directory traversal flaw.
You are affected if the Sc Filechecker component is installed with version 0.6 or lower and the file path input feature is accessible to users who could supply paths containing '../' sequences.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict path validation to canonicalize and verify that resolved file paths remain within the intended base directory before processing. Reject any paths containing directory traversal sequences.
Fix this in Sc Filechecker
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35743 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-35743 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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