Vulnerability in LimeSurvey Community Edition (CVE-2026-65931)
Summary
Vulnerability in LimeSurvey Community Edition (CVE-2026-65931). Risk of unauthorized operations or information disclosure. Exploitable via POST /index.php/admin/menuentries/sa/create.
Original description
The description as published by the source.
LimeSurvey Community Edition 7.0.5 contains an authenticated improper authorization vulnerability in the survey menu entry creation endpoint.
An authenticated user with only the global settings:read permission can directly invoke POST /index.php/admin/menuentries/sa/create and create new survey menu entries without the expected settings:update privilege. The endpoint also allows the attacker to submit menu IDs that the normal interface and intended update workflow restrict for non-superadministrators, enabling unauthorized changes to administrative navigation records.
This issue affects LimeSurvey: 7.0.5.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-65931 has been found in LimeSurvey Community Edition.
Attackers can target a specific entry point like POST /index.php/admin/menuentries/sa/create over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "LimeSurvey Community Edition CVE-2026-65931" on the vendor's site.
CVE-2026-65931 (LimeSurvey Community Edition) — CWE-862
Attack surface: POST /index.php/admin/menuentries/sa/create
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in LimeSurvey Community Edition. Attackers reach the vulnerable code path via POST /index.php/admin/menuentries/sa/create.
Check the vendor advisory for the affected versions of LimeSurvey Community Edition. Attack surface: POST /index.php/admin/menuentries/sa/create.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /index.php/admin/menuentries/sa/create requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで LimeSurvey Community Edition を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'POST /index.php/admin/menuentries/sa/create' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /index.php/admin/menuentries/sa/createへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /index.php/admin/menuentries/sa/create on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory fluidattacks.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com