Repository navigation
OpenPorte release v1.30.3
OpenPorte is a privacy-friendly, self-hostable spam protection and CAPTCHA plugin for WordPress — a community-maintained, fully open-source (GPLv2 or later) fork of ALTCHA Spam Protection v1.
OpenPorte 1.30.3 is a security release. Please update now. It fixes a high-severity vulnerability on sites that use Contact Form 7 or HTML Forms.
Security
GHSA-hvr5-q69x-jp62: unauthenticated arbitrary shortcode execution through Contact Form 7 and HTML Forms. High, CVSS 3.1 7.3, CWE-94.
To show the widget in those forms, OpenPorte expanded every shortcode in the displayed form, including text that visitors had typed into its fields or put in the page's URL. So any visitor, without logging in, could make the site run any shortcode registered on it. Depending on the plugins installed, this could expose private content or open the way to flaws in other plugins' shortcodes. Neither the integration settings nor the CAPTCHA prevented it.
- Affected:
- OpenPorte Spam Protection ≤ 1.30.2, on sites with Contact Form 7 or HTML Forms active, whatever the integration setting.
- ALTCHA Spam Protection ≤ 1.26.3 (its last GPL release), the plugin OpenPorte forked. The flaw dates back to its 1.6.0 (Contact Form 7) and 1.7.0 (HTML Forms).
- Fixed in: OpenPorte 1.30.3. OpenPorte now renders only its own
[openporte]and[altcha]tags, and only from the form as the site admin wrote it. - ALTCHA Spam Protection users: that plugin is no longer maintained and gets no fix. Move to a maintained plugin, such as the latest ALTCHA for WordPress or OpenPorte ≥ 1.30.3. OpenPorte imports ALTCHA Spam Protection 1.x settings and keeps its free, self-hosted features backward compatible, including the
[altcha]shortcode; the paid altcha.org SaaS mode was not carried over. OpenPorte is not affiliated with or endorsed by ALTCHA. - Thanks to @Erik-Debye for the responsible report.
Changes highlights
- Security fix: see above.
- Contact Form 7:
[openporte]and[altcha]are now Contact Form 7 form-tags. Write the widget language as[openporte language:de_DE]; the old[openporte language="de_DE"]keeps working.
Backward compatibility
- Other plugins' shortcodes in Contact Form 7 and HTML Forms forms are no longer rendered. Neither form plugin renders shortcodes in its forms itself; it only worked as a side effect of the vulnerable code. There is deliberately no setting to bring it back, as it would re-open the vulnerability. If one of your forms relied on it, see the FAQ entry "Shortcodes in my Contact Form 7 or HTML Forms form stopped working. Why?" and ask in the support forum: we will help you find a safe way.
- Contact Form 7: a tag that mixes another quoted attribute with
language="…"(for example[openporte mode="…" language="de_DE"]) loses its language. Use[openporte language:de_DE]. The tag has nomode: the widget uses the mode set in OpenPorte's settings.
Otherwise, same as release v1.30.2.
Upgrading
Update through your WordPress dashboard or download the zip below. No setting changes. If you have Contact Form 7 or HTML Forms forms, check that they still look as expected.
Deprecations
None in this release. The deprecations in place since v1.28.0 and v1.29.0 are unchanged.
Known issues
- HTML Forms: with the integration on, a form that also contains
[openporte]shows two widgets. Remove the tag from the form, or switch the integration off (#148, planned for 1.31.0). - WooCommerce Registration Protection: accounts created during an order (classic or block checkout, order confirmation page) show no widget and are not challenged. The My Account registration form remains protected (#142, planned for 1.31.0).
- WPForms: the form's styling reset strips the widget's border and footer styles. The widget still works; only its look is affected (#138, planned for 1.31.0).
Changelog
- Fix shortcode execution through form integrations (GHSA-hvr5-q69x-jp62) by @jcberthon
Full Changelog: v1.30.2...v1.30.3
Contributors
Contributors (GitHub) for this release: @jcberthon.
Vulnerability report: @Erik-Debye.
Co-contributors: Claude Code / @claude (AI).
Resolved issues
None. The fix was prepared privately in the security advisory.