Loading vulnerability…
PolarLearn is a free and open-source learning program. Prior to version 0-PRERELEASE-15, the vote API route (POST /api/v1/forum/vote) trusts the JSON body’s direction value without runtime validation. TypeScript types are not enforced at runtime, so an attacker can send arbitrary strings (e.g., "x") as direction. Downstream (VoteServer) treats any non-"up" and non-null value as a downvote and persists the invalid value in votes_data. This can be exploited to bypass intended business logic. Version 0-PRERELEASE-15 fixes the vulnerability.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Repository contains a minimal proof-of-concept for CVE-2026-25126 (PolarLearn vote count manipulation via business-logic flaw). Structure: (1) README.md explains the vulnerability: the forum voting API deserializes JSON into a TypeScript-typed object without runtime validation; downstream logic treats unexpected non-null 'direction' values as a downvote and persists them. By alternating an invalid direction with a null reset, a single authenticated user can repeatedly decrement a post’s vote count. (2) poc.js is the executable PoC (Node.js 18+). It defines POST_ID, TARGET_URL (https://polarlearn.nl/api/v1/forum/vote), and COOKIE (authenticated session). In runTest(), it performs 5 cycles; each cycle sends two POST requests with JSON bodies: {postId, direction:"invalid_direction"} then {postId, direction:null}. If both responses are OK, it reports the vote count should have dropped by 1. No reverse shell or code execution is involved; the capability is limited to authenticated API abuse to manipulate application state (vote totals).
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.