cmseek
1.1.3 open-sourceThe section your link pointed to isn't on cmseek's page any more, so we've brought you to the top.
CMSeeK is a CMS detection and exploitation suite that scans WordPress, Joomla, Drupal, and over 180 other content management systems.
python3 cmseek.py --only-cms -u https://example.com python3 cmseek.py --light-scan -u https://example.com python3 cmseek.py -u https://example.com --only-cms --light-scan cmseek -u <target> --light-scan cmseek -u <target> --only-cms cmseek --url https://example.com --googlebot cmseek --url https://example.com/landing --no-redirect cmseek -l targets.txt cmseek.py --url https://example.com --random-agent --verbose cmseek.py --url https://example.com --user-agent 'Mozilla/5.0 (Windows NT 10.0; Win64; x64)'
Summary
cmseek is an open-source command-line tool that fingerprints content management systems on a target website, detecting over 180 CMS platforms and running deep scans against WordPress, Joomla, and Drupal to pull version numbers, enumerate users, plugins, and themes, and flag known vulnerabilities. It is free to use, invoked against a single URL or a list of sites read from a file, with options for custom or randomised user agents and verbose output. The audience is penetration testers and web-recon practitioners doing reconnaissance before deeper application testing, and it sits in the CMS-fingerprinting corner of web-app security rather than general vulnerability scanning. First committed in 2018 and still maintained by its community, though with only one commit in the past year, it has settled into a slow, low-activity phase rather than an actively evolving one.
CMSeeK is a CMS detection and exploitation suite that scans WordPress, Joomla, Drupal, and over 180 other content management systems.
How cmseek helps
What content management system is this website actually running?
crawls the target URL and matches signatures against a database of over 180 CMS platforms, naming the CMS it detects rather than guessing from surface branding
What version of WordPress, Joomla, or Drupal is exposed, and does it have known vulnerabilities?
runs a deep scan specific to that platform, pulling the version string and cross-checking it against vulnerability data to flag known flaws
Which user accounts, plugins, and themes can an outsider already see on this WordPress site?
enumerates users through multiple detection methods and lists installed plugins and themes without needing authenticated access
Are there leftover backup files, exposed config, or an open admin page on this Joomla install?
checks the site for backup file remnants, config leaks, directory listing, and the admin login location, reporting each one found
Can a list of client sites be triaged for CMS exposure in one pass?
reads targets from a file and repeats the same detection and deep-scan logic across each one, so results come back per-site instead of one URL at a time
Will repeated scans from this machine get blocked or fingerprinted as a bot?
lets each request go out with a custom or randomised user agent so the scan traffic doesn't look identical across targets
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for cmseek, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail cmseek puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Coverage
Missing something? Tell us
What cmseek connects to, runs on and detects, read from its release notes and docs. So far: 2 new detections, 1 updated integration.
3 changes, tracked since Oct 4, 2026.
-
Oct 42026
new New CMS fingerprints
Covers 12: Smartstore, Solusquare Commerce Cloud, Spree, Brightspot CMS, Amiro.CMS, Weebly and 6 more
-
Oct 42026
new Version detection for Amiro.CMS and GoDaddy Website Builder
Version detection added for: - Amiro.CMS - GoDaddy Website Builder
-
Oct 42026
updated WordPress vulnerability source switched to wpvulns.com
Switched to wpvulns.com for wordpress vulnerabilities
Vulnerability & code scanning 1
Nothing first seen in this window. That doesn't mean cmseek shipped nothing, only that we found no record of it.
How we count
Read from 1 of 20 release notes and docs updates we hold for cmseek. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through cmseek's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Releases
20 entries
No entries match these filters.
- October 20261
- September 20262
- July 20202
- May 20192
- February 20192
- August 20187
- July 20184
Project health
Issue, contributor and maintainer activity in Tuhinshubhra/CMSeeK, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 2 +2 vs prior 12 months
- Maintainers 0 +0 joined · −0 left, last 12 months
- Bus factor 0 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close < 1 day first maintainer reply 0.1 hours
- Open backlog 31 of 150 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 31
- Contributors / month 0
- Commits / month 0
- Stars 2,578
- other 100%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.