CVE-2025-67031
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedORSEE (Online Recruitment System for Economic Experiments) 3.1.0 contains an authenticated Remote Code Execution vulnerability in the participant profile field processing subsystem. Certain field configurations accept values beginning with the prefix "func:" which are passed directly into an eval() call inside tagsets/participant.php and tagsets/options.php.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceORSEE 3.1.0 has an authenticated RCE in the participant profile field processing. Fields accepting 'func:' prefix values pass them directly to eval() in tagsets/participant.php and tagsets/options.php, allowing arbitrary code execution by authenticated users.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify ORSEE versionCheck the installed version by examining the README file, version.php, or the admin panel's 'About' section. Look for a file named version.php in the root or includes directory, or check the footer of admin pages.Affected if The installed version is 3.1.0 exactly.
-
Locate vulnerable PHP filesSearch the webroot for the files tagsets/participant.php and tagsets/options.php. These should exist in a subdirectory named 'tagsets' relative to the ORSEE installation root.Affected if Both files exist in the expected location.
-
Inspect participant.php for unsafe eval()Open tagsets/participant.php and search for eval() function calls. Look for code patterns where user-supplied input (particularly from field values) is passed to eval() without sanitization.Affected if The file contains eval() calls that process values containing 'func:' prefix.
-
Inspect options.php for unsafe eval()Open tagsets/options.php and search for eval() function calls. Look for similar patterns where 'func:' prefixed values are evaluated.Affected if The file contains eval() calls that process values containing 'func:' prefix.
-
Verify participant field configuration accessLog in as an authenticated user and navigate to the participant field configuration area (typically under Tagsets or Participant Fields in the admin panel). Check if the user can create or edit fields that accept 'func:' prefixed values.Affected if Authenticated users with participant field configuration permissions can access the vulnerable feature.
If the installed ORSEE version is 3.1.0, the vulnerable eval() calls with 'func:' prefix exist in tagsets/participant.php or tagsets/options.php, and an authenticated user has access to participant field configuration, the environment is affected by this CVE.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace unsafe eval() calls with safe alternatives (e.g., defined whitelist of functions, preg_replace callbacks, or custom expression parsers). Restrict participant field configuration permissions to trusted admins only until patched.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67031 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-67031 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data