CVE
SurveyKing authorization bypass in linked survey feature
Affects SurveyKing 1.12.0 through 1.13.2 with the linked survey feature in use. The checked facts list no fixed version.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. SurveyKing 1.12.0 through 1.13.2 with the linked survey feature in use
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 20/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
SurveyKing, by javahuang, has an authorization bypass in its linked survey feature. A remote attacker with a low-privilege logged-in account can point a linked option at another user's survey and read, change, or add responses in that survey.
Read the original description
SurveyKing 1.12.0 through 1.13.2 contains an authorization bypass in the linked survey feature that fails to verify the referenced linkSurveyId belongs to the caller's own project. Authenticated attackers can point a linked option at another user's survey so that loadLinkResult and updateLinkSurveyAnswer read, rewrite, or create responses in that survey.
Who should check
Teams running SurveyKing 1.12.0 through 1.13.2 that use the linked survey feature
Read the source excerpt
“SurveyKing 1.12.0 through 1.13.2 contains an authorization bypass in the linked survey feature”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch5/5No patch listed yet
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 27 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
SurveyKing 1.12.0 through 1.13.2 with the linked survey feature in useWorkaround: The checked facts give no workaround. Limiting or disabling the linked survey feature would remove the affected functionality, but the facts do not state this as a vendor-recommended workaround.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129153 (SurveyKing 1.12.0 through 1.13.2 Authorization Bypass via Linked Survey linkSurveyId), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129153 (entry last updated 2026-11-13):
Affected:
- javahuang SurveyKing: from 1.12.0, through 1.13.2
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- SurveyKing 1.12.0 through 1.13.2 with the linked survey feature in use (source: https://www.vulncheck.com/advisories/surveyking-1.12.0-through-1.13.2-authorization-bypass-via-linked-survey-linksurveyid)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-129153 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129153 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/javahuang/SurveyKing/issues/92
- https://vul.yulun.ac.cn/20261107/surveyking/
- https://github.com/javahuang/SurveyKing/blob/5de0d05b682ee34244c0b6c07be24eb6358cd8a5/server/rdbms/src/main/java/cn/surveyking/server/impl/SurveyServiceImpl.java#L435-L470
- https://github.com/javahuang/SurveyKing/blob/5de0d05b682ee34244c0b6c07be24eb6358cd8a5/server/rdbms/src/main/java/cn/surveyking/server/impl/AnswerServiceImpl.java#L793-L830
- https://www.vulncheck.com/advisories/surveyking-1.12.0-through-1.13.2-authorization-bypass-via-linked-survey-linksurveyid
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129153
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129153"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- javahuang SurveyKing
From 1.12.0 · through 1.13.2
Evidence 7
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 5
- Report
- Repository
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129153
Is CVE-2026-129153 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An authenticated user can reach responses in another user's survey through the linked survey feature. The loadLinkResult and updateLinkSurveyAnswer functions can read, rewrite, or create responses in that survey.Source: vulncheck.com
Which versions are affected by CVE-2026-129153?
SurveyKing: from 1.12.0 through 1.13.2.Source: cve.now feed data
Am I affected, and how do I check?
SurveyKing versions 1.12.0 through 1.13.2 are affected when the linked survey feature is in use. To check a setup, confirm the installed SurveyKing version and whether linked surveys are used.Source: vulncheck.com
How do I fix CVE-2026-129153?
The checked facts name no fixed version or patch, so no upgrade target can be given from them. Check the vendor's advisory for a fix before relying on any version.Source: vulncheck.com
What if there's no patch?
The checked facts give no workaround. Limiting or disabling the linked survey feature would remove the affected functionality, but the facts do not state this as a vendor-recommended workaround.Source: vulncheck.com