WordPress GS Testimonial Slider plugin <= 3.3.10 - PHP Object Injection vulnerability
Affects the GS Testimonial Slider WordPress plugin, version 3.3.10 and earlier. No official fix is available yet.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Contributor PHP Object Injection in GS Testimonial Slider <= 3.3.10 versions.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- gs-testimonial
through 3.3.10
References 1
Questions about CVE-2026-78527
What does this mean?
PHP Object Injection lets an attacker manipulate how the site processes data, which can lead to harmful actions running on the server.Source: patchstack.com
Am I affected, and how do I check?
GS Testimonial Slider plugin versions up to and including 3.3.10 are in scope. To check a site, look at the plugin version shown on the WordPress Plugins screen.Source: patchstack.com
What should I do about it?
The advisory names no fixed version and no official patch exists yet. Watch for an official plugin update later than 3.3.10 and install it once it is released.Source: patchstack.com
Is it 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 if there's no patch?
A Patchstack mitigation rule blocks attacks until an official patch becomes available. That rule is the only workaround listed in the facts.Source: patchstack.com