PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-67350 s9y CVE debrief

CVE-2026-67350 is an open redirect vulnerability in Serendipity's exit.php file when the Track Exits plugin is configured with commentredirection set to s9y. This allows unauthenticated attackers to redirect users to arbitrary external sites by supplying a malicious Base64-encoded url parameter. The vulnerability has a CVSS score of 2.1 and is considered low severity.

Vendor
s9y
Product
Serendipity
CVSS
LOW 2.1
CISA KEV
Not listed in stored evidence
Original CVE published
2026-07-31
Original CVE updated
2026-09-09
Advisory published
2026-07-31
Advisory updated
2026-09-09

Who should care

Defenders responsible for Serendipity installations, particularly those using the Track Exits plugin, should assess exposure and verify configurations to prevent potential phishing attempts and URL reputation filter bypasses.

Why it matters

CVE-2026-67350 is a low-severity open redirect vulnerability in Serendipity's exit.php file that allows unauthenticated attackers to redirect users to arbitrary external sites. Defenders should prioritize verifying configurations and monitoring for potential phishing attempts and URL reputation filter bypasses.

  • Phishing attempts may be conducted using trusted-looking URLs leveraging the legitimate blog domain
  • Malware delivery may be facilitated through the open redirect vulnerability
  • URL reputation filters may be bypassed using the vulnerability
  • Verification of the Track Exits plugin configuration and commentredirection setting is required

Technical summary

The vulnerability exists in the exit.php file of Serendipity when the Track Exits plugin is configured with commentredirection set to s9y. An unauthenticated attacker can supply a malicious Base64-encoded url parameter to redirect users to arbitrary external sites. This allows attackers to conduct phishing, deliver malware, or bypass URL reputation filters using trusted-looking URLs leveraging the legitimate blog domain. Defenders should prioritize verifying configurations and monitoring for potential phishing attempts and URL reputation filter bypasses.

Defensive priority

Defenders should prioritize verifying the configuration of the Track Exits plugin in Serendipity installations and ensuring that the commentredirection setting is not set to s9y. Additionally, defenders should monitor for potential phishing attempts and URL reputation filter bypasses.

Recommended defensive actions

  • Verify the configuration of the Track Exits plugin in Serendipity installations
  • Ensure that the commentredirection setting is not set to s9y
  • Monitor for potential phishing attempts and URL reputation filter bypasses
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected product. However, the corpus does not establish versions, exploitation, impact, or remediation, which require verification from the supplied official sources.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-67350 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-67350

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-67350 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-67350

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.