CVE-2026-6573
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 · uneditedA vulnerability was detected in PHPEMS 11.0. This affects the function temppage of the file /app/exam/controller/exams.master.php of the component Instant Exam Creation Handler. The manipulation of the argument uploadfile results in server-side request forgery. The attack can be executed remotely. The exploit is now public and may be used.
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 · moderate confidencePHPEMS 11.0 contains a server-side request forgery (SSRF) vulnerability in the temppage function of /app/exam/controller/exams.master.php. The uploadfile parameter is not properly validated, allowing an attacker to induce the server to make arbitrary HTTP requests to internal or external resources.
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.
-
Confirm PHPEMS version 11.0 is installedLocate the PHPEMS installation directory and check the version file (commonly version.php, changelog, or composer.json). Run: find /path/to/webroot -name '*.php' -path '*/includes/*' | head -5 to locate version indicators, or check admin panel if available.Affected if The installed version is PHPEMS 11.0 exactly.
-
Verify vulnerable file existsCheck if /app/exam/controller/exams.master.php exists in the web root. Run: ls -la /path/to/webroot/app/exam/controller/exams.master.phpAffected if The file exists and the installation is PHPEMS 11.0.
-
Confirm temppage function is web-accessibleReview the exams.master.php source code to see if the temppage function is publicly accessible (not protected by authentication or access control). Check for missing @auth, @login annotations or role checks within the function definition.Affected if The temppage function has no authentication or authorization checks.
-
Inspect uploadfile parameter handlingOpen /app/exam/controller/exams.master.php and locate the temppage function. Search for the uploadfile parameter usage. Check if it undergoes any URL/domain validation before being used in file_get_contents, curl, or similar HTTP request functions.Affected if The uploadfile parameter is passed directly to HTTP request functions without validation, or validation is missing/weak.
-
Identify exposed attack surfaceCheck web server configuration (Apache/nginx) to confirm routes to /app/exam/controller/ are not blocked. Identify the URL pattern that invokes temppage (typically index.php?app=exam&controller=exams&action=temppage or similar).Affected if The temppage action is reachable via HTTP without restriction.
A user is affected if they run PHPEMS 11.0 with the exams.master.php file present and the temppage function accessible without proper validation on the uploadfile parameter.
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 dataImplement strict validation of the uploadfile parameter to restrict URLs to expected domains/ports, or replace the SSRF-vulnerable file upload mechanism with a safe alternative that avoids processing user-supplied URLs.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6573 — 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-2026-6573 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