Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2026-129493 — Proof-of-concept lab and Python driver for CVE-2026-129493: leaks bolo-solo articleViewPwd from the public GET /articles endpoint and unlocks protected articles via /console/article-pwd. | Kitploit
Tools/GitHubGitHub/googlesky/cve-2026-129493
Vulnerability AnalysisExploitationWeb Application ExploitationInformation GatheringSecurity VirtualizationWeb SecurityLabs & Practice
GitHubgooglesky/cve-2026-129493

CVE-2026-129493

Proof-of-concept lab and Python driver for CVE-2026-129493: leaks bolo-solo articleViewPwd from the public GET /articles endpoint and unlocks protected articles via /console/article-pwd.

View Repository
3 days agoNot yet reviewed
Website

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    936
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    555
  • 3

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    353
  • 4

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    348
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    336
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    288

Explore all tools

Browse our collection of tools

View all tools →
Share

CVE-2026-129493 — Bolo (bolo-solo): the public /articles endpoint discloses article view passwords

License: MIT Research status: validated

CVECVE-2026-129493 (VDB-437424)
Componentbolo-blog/bolo-solo — ArticleProcessor.getArticlesByPage (public GET /articles)
Affected1.7 – 2.6.4 (the release at the advisory's commit is the affected one; unfixed upstream)
Fixed inno upstream fix at publication time; the fixed side is a hash-checked synthetic remediation (documented as such)
CWECWE-200 (Exposure of Sensitive Information)
ImpactThe plaintext articleViewPwd of every password-protected article ships to any anonymous visitor of /articles; submitting it to /console/article-pwd renders the protected content readable — the view-password confidentiality boundary is void
VectorNetwork, unauthenticated — one GET
Triggerany password-protected article in the paged listing

ArticleQueryService has a dedicated scrubber, removeUnusedProperties(JSONObject), that strips ARTICLE_VIEW_PWD (among other internals) before articles are handed to renderers. The paginated query path used by the public endpoint never runs it:

// ArticleQueryService.getArticles(requestJSONObject) — no removeUnusedProperties call
// ArticleProcessor.getArticlesByPage (the public GET /articles):
final JSONObject result = articleQueryService.getArticles(requestJSONObject);
final List<JSONObject> articles = CollectionUtils.jsonArrayToList(result.getJSONArray(Article.ARTICLES));
dataModelService.setArticlesExProperties(context, articles, preference);
jsonObject.put(Keys.RESULTS, result);

so the raw rows — articleViewPwd included — go into the anonymous JSON response. This laboratory runs the real bolo-solo v2.6.4_stable (the upstream Maven build, embedded H2) and proves the full chain: create a protected article → leak its password from /articles → unlock it via /console/article-pwd → read the protected content.


1. Root cause

Two facts compose:

  1. getArticlesByPage is the public, unauthenticated listing endpoint;
  2. the paginated getArticles(JSONObject) path does not pass its rows through removeUnusedProperties, unlike the single-article and random/relevant paths which do.

The password-verification flow (POST /console/article-pwd with articleId + pwdTyped) accepts any caller's password guess and stores the unlock in that caller's session — so the leaked password converts directly into read access. Protected content, comments, and any future "password-gated" features share the same boundary.

2. Reproduction environment

serviceimagerole
bolo-vulncve-2026-129493:vulnbolo-solo v2.6.4_stable as released (upstream build recipe)
bolo-fixedcve-2026-129493:fixedsame tree + lab/patch-fixed.py (hash-checked): the paged response strips articleViewPwd
poccve-2026-129493-poc:localstdlib-only Python driver

The instance bootstraps through the product's own first-run flow (POST /oauth/bolo/login creates the admin; the second login sets the session cookie — upstream behaviour), uses the embedded H2 database via the docker profile, and the admin article API creates the protected article exactly as the admin console does.

3. Running the environment

./run-lab.sh build     # upstream bolo build at v2.6.4_stable (both trees)
./run-lab.sh up        # cve129493lab network, bolo-vuln, bolo-fixed
./run-lab.sh sweep     # check / exploit / probe / mitigation on both sides
./run-lab.sh down

4. The PoC

poc/poc.py (stdlib only):

  • check — bootstrap + create a protected article + one anonymous GET /articles; classification by password presence. Exit 1 vulnerable, 0 safe, 3 no worker, 2 unreachable.
  • exploit — full chain: leak the password from the public JSON, then POST /console/article-pwd and read the protected article at its permalink.
  • probe — endpoint matrix: /articles, /articles/1, tag pages.
  • mitigation — no upstream fix; the fixed container is the form a fix takes (scrub the field in the paged response).

5. Expected results

runbolo-vuln (v2.6.4)bolo-fixed (synthetic)
checkHTTP 200, articleViewPwd":"s3cret-view-pass" presentpassword absent
exploitpassword leaked → article unlocked → protected content readno leak
probe /articles, /articles/1, tags/articles leaks; others 404no leak anywhere
mitigationleakssafe

Captured runs: evidence/check-*-run.txt, evidence/exploit-*-run.txt, evidence/probe-*-run.txt, evidence/mitigation-*-run.txt, evidence/versions.txt, evidence/0day-sweep.txt.

6. Environment preconditions

  • Podman (or Docker) with network-creation rights; every container bounded on the isolated cve129493lab network.
  • Outbound HTTPS at image build (GitHub: bolo-solo v2.6.4_stable; Maven Central). The Maven build takes several minutes.

7. Additional findings (0-day sweep on the fixed line)

The endpoint matrix is the surface sweep (evidence/0day-sweep.txt): on the remediated build no public endpoint exposes the view password; on the shipped build exactly one form (GET /articles) does — no second disclosure path was found. The sibling stored-XSS flaw in the same product is CVE-2026-129492, reproduced in CVE-2026-129492.

8. Repository layout

README.md             this write-up
run-lab.sh            environment driver (build / up / sweep / down)
Makefile              convenience targets
poc/poc.py            the PoC (check / exploit / probe / mitigation)
poc/Dockerfile        runner image (python:3.12-alpine)
lab/lab.Dockerfile    multi-stage build (bolo v2.6.4_stable, both trees)
lab/patch-fixed.py    the hash-checked synthetic remediation
lab/entrypoint.sh     standalone Starter
evidence/             captured runs of every mode on both sides
TRACKING.md           excluded (working record)

9. References

  • CVE record — https://www.cve.org/CVERecord?id=CVE-2026-129493
  • VulDB entry — https://vuldb.com/?q=CVE-2026-129493
  • Advisory — https://vul.yulun.ac.cn/20261115/bolo-solo/
  • bolo-solo — https://github.com/bolo-blog/bolo-solo (issue #331)
Download Tool