Gtbabel

Gtbabel has one disclosed vulnerability in the WordSec catalog, all reported in 2025; it is fixed as of September 2026. Their average CVSS score is 7.5, and the most serious one scores 7.5 out of 10. Severity breakdown: 0 critical and 1 high.

The most common weakness is Sensitive Cookie In HTTPS Session Without 'Secure' Attribute, behind 1 of the records (100%).

The one issue recorded for Gtbabel has a vendor fix available, so running the current release closes it.

All of these findings were reported by Hassan Khan Yusufzai - Splint3r7. The current release is tested up to WordPress 7.1.

Strategic Overview

Avg CVSSHigh

7.5/ 10

Patch Coverage100%

Open

Fixed

Get automatic notifications for all Gtbabel vulnerabilities before they are exploited.

Highest severity on recordCVSS 7.5CVE-2024-11638

Gtbabel <= 6.6.8 - Unauthenticated Cookie Stealing

Read the full analysis

Vulnerability Records

1 records


2025-02-17 00:00	Gtbabel <= 6.6.8 - Unauthenticated Cookie Stealing Gtbabel <= 6.6.8	`CVE-2024-11638`	7.5 High	Hassan Khan Yusufzai - Splint3r7	Yes

Showing 1–1 of 1 reports

Latestv6.9.2

Gtbabel

Author

gtbabel

0.0(0)

0/100

Last Updated

2026-08-29 (15d ago)

Active Installs

Downloads

7,421

Requires WP

5.3.2+

Requires PHP

8.5+

Tested up to

WP 7.1

Created

2020-03-14 (7y ago)

Gtbabel extracts on every page load any page into logical paragraph tokens. Static and dynamic content is deliberately treated the same. All tokens are replaced (if available) by it’s translation before rendered. The tokens get dumped (if not available) into gettext, where they can be translated.

View on WordPress.org