CVE-2010-0989
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 · uneditedDirectory traversal vulnerability in delete.php in Pulse CMS before 1.2.3 allows remote authenticated users to delete arbitrary files via directory traversal sequences in the f parameter.
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 confidenceDirectory traversal vulnerability in Pulse CMS delete.php allows authenticated users to delete arbitrary files by injecting path traversal sequences (e.g., ../../../) into the f parameter. The application fails to properly validate or sanitize file paths before performing deletion operations.
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<= 1.2.2= 1.0= 1.1= 1.01= 1.2= 1.2.1= 1.15= 1.16= 1.17= 1.18CVSS 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
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:S/C:P/I:P/A:N
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.
-
Identify Pulse CMS versionLocate the version file or version identifier in your Pulse CMS installation (commonly found in a config file, version.php, or in the admin panel footer). Compare the installed version against the affected range: versions 1.0, 1.01, 1.1, 1.2, 1.2.1, 1.2.2, 1.15, 1.16, 1.17, and 1.18 are all vulnerable.Affected if The installed version is 1.2.2 or earlier, or matches any of the specific versions listed (1.0, 1.01, 1.1, 1.15, 1.16, 1.17, 1.18).
-
Locate delete.phpFind the delete.php file within your Pulse CMS installation directory.Affected if The delete.php file exists in the application root or admin directory.
-
Verify authentication is enforcedCheck if the admin panel and delete functionality require valid user authentication. Attempt to access the delete.php endpoint without logging in or examine the authentication logic in the code.Affected if The delete.php endpoint is accessible without authentication OR allows authenticated users to manipulate the f parameter.
-
Check for path traversal protectionReview the delete.php source code to see if it validates or sanitizes the f parameter to prevent directory traversal sequences (such as ../ or ..\).Affected if The code does not validate that the f parameter points to a file within the allowed directory, allowing path traversal sequences.
You are affected if your Pulse CMS installation runs version 1.2.2 or earlier, contains the delete.php file, and the application either lacks authentication for delete operations or fails to sanitize path traversal sequences in the f parameter.
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 dataUpgrade to Pulse CMS 1.2.3 or later which contains the fix. Alternatively, implement strict input validation ensuring the f parameter cannot contain traversal sequences and restrict delete functionality to authorized users only.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-0989 — 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-2010-0989 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