LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25126: PolarLearn's unvalidated vote direction allows vote count manipulation

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.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-25126 lets authenticated users manipulate PolarLearn forum vote counts by sending unexpected vote direction values. The issue affects PolarLearn before 0-PRERELEASE-15 and is fixed in 0-PRERELEASE-15. Business impact is mainly integrity: forum voting or reputation signals may be unreliable if abused.

Executive priority

Prioritize remediation if PolarLearn forums influence learning outcomes, moderation, reputation, or user trust. The issue is high severity but scoped to vote integrity, not confirmed remote code execution or active exploitation based on provided sources.

Technical view

The POST /api/v1/forum/vote route relied on TypeScript typing without runtime validation of the JSON direction field. Downstream logic treated any value other than "up" or null as a downvote and stored invalid values in votes_data. This is CWE-20 improper input validation with CVSS 3.1 score 7.1.

Likely exposure

Exposure is limited to organizations running PolarLearn versions before 0-PRERELEASE-15, with users able to access the forum voting API. The CVSS vector requires low privileges, no user interaction, and network access.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not listed as KEV in the bundle. Abuse requires an authenticated or otherwise low-privileged user with access to the vote API. Impact is vote manipulation and possible trust degradation in forum ranking or moderation signals.

Researcher notes

The vulnerability is an application logic flaw caused by missing runtime validation. The advisory identifies the vulnerable API route and downstream handling in VoteServer. Validate the fixed version behavior without publishing payloads or automated abuse methods.

Mitigation direction

  • Upgrade PolarLearn to version 0-PRERELEASE-15 or later.
  • Review the GitHub advisory and fixing commit for vendor-specific remediation details.
  • Treat vote-derived reputation or ranking data as potentially unreliable until reviewed.
  • If upgrade is delayed, check vendor guidance for supported temporary controls.

Validation and detection

  • Confirm deployed PolarLearn version is 0-PRERELEASE-15 or later.
  • Verify forum voting input validation rejects unexpected direction values.
  • Review votes_data for stored values outside expected vote states.
  • Assess whether manipulated votes affected moderation, ranking, or user trust decisions.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-20: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-25126 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N2.84.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2026-25126Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
polarnlPolarLearn< 0-PRERELEASE-15Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.