WordPress Tickera plugin <= 3.6.0.2 - PHP Object Injection vulnerability

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Tickera/Tickera (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Tickera/Tickera.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Aug 31, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Aug 31, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Aug 31, 2026

Sources and claim methodology

• Source referencepatchstack.com

Related CVEs

• Wallos: Unauthenticated database replacement via import endpoint on fresh installSame generic ecosystem
• Wallos: SSRF via Test Email Notification - unvalidated SMTP host/portSame generic ecosystem
• Wallos: Zip Slip path traversal in database restore writes files to webrootSame generic ecosystem
• Wallos: SSRF via OIDC Token/UserInfo URL ConfigurationSame generic ecosystem
• Wallos: OIDC account takeover via email-based account linking without `email_verified` checkSame generic ecosystem
• Smarty: SSRF via redirect bypass of trusted_uri using {fetch}Same generic ecosystem