CVE-2026-96768 softaculous CVE debrief

Who should care

Defenders responsible for WordPress installations using the GoSMTP Pro plugin should assess exposure and prioritize verification of plugin versions. They should also review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. Additionally, defenders should plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Why it matters

The GoSMTP Pro plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content, allowing unauthenticated attackers to inject web scripts. Defenders should prioritize verifying exposure and assessing the risk of arbitrary script injection.

• Unauthenticated attackers can inject web scripts that execute when a user accesses an injected page
• Defenders must verify exposure of WordPress installations using GoSMTP Pro plugin version 1.2.3 or earlier
• The vulnerability allows for arbitrary script injection, which can lead to further exploitation

Technical summary

The GoSMTP Pro plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content in all versions up to, and including, 1.2.3. This allows unauthenticated attackers to inject web scripts that execute when a user accesses an injected page. The vulnerability is caused by insufficient input sanitization and output escaping, and the exploit is made possible by WordPress comment kses not stripping entity-encoded tag delimiters. The plugin's email log database table stores the injected scripts, which can be executed when a user accesses an injected page.

Defensive priority

Defenders should prioritize verifying exposure of WordPress installations using GoSMTP Pro plugin version 1.2.3 or earlier and assess the risk of arbitrary script injection.

Recommended defensive actions

• Verify WordPress installations for GoSMTP Pro plugin version 1.2.3 or earlier
• Assess the risk of arbitrary script injection
• Consider upgrading to a patched version of the plugin
• 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 description provides details on the vulnerability, including the affected plugin version and the type of attack possible. However, the corpus does not provide information on known exploitation or affected deployments.

Sources and 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.