Is IF AS Shortcode safe to use?

Laskyr does not give safety verdicts. The latest version (1.2) has 1 known unpatched vulnerability. As of 2026-11-04, the sources we check list the newest release of IF AS Shortcode as affected and name no fixed version yet. Keep IF AS Shortcode on the latest version (1.2) and remove it if you do not use it.

Which versions of IF AS Shortcode are vulnerable?

Known issues on record (newest first): Remote code execution (1.2 and older). The full list with sources is on this page.

What is the latest version of IF AS Shortcode?

1.2, according to wordpress.org (last updated 2024-08-09). It has 10+ active installs.

What should I do if my IF AS Shortcode is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update if-as-shortcode). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · if-as-shortcode · data as of 2026-11-04

Is IF AS Shortcode safe? Known vulnerabilities and latest version

Latest version: 1.2
Last updated: 2024-08-09
Active installs: 10+
Known issues on record: 1
Unpatched in latest: 1
Tested up to WP: 6.6.11 · PHP 5.6+

You can use if statement as shortcode everywhere you want! — by Mohammad I. Okfie

What to do

There is no fixed version yet. If you can live without IF AS Shortcode for now, deactivate it and delete it until the developer ships a fix.
If you must keep it, limit who can log in (remove unused accounts, especially low-level ones) and put a web application firewall in front of the site.
Watch for an update: get an email when this page changes.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.

With WP-CLI: wp plugin get if-as-shortcode --field=version shows what you run; wp plugin update if-as-shortcode updates it.

Check your version

Known vulnerabilities

1 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

critical 9.9 affects latest 1.2 CVE-2025-68897 · published 2025-12-29

Remote code execution in IF AS Shortcode (1.2 and older)

Affected: 1.2 and older
Fixed in: no fix listed yet
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Improper Control of Generation of Code ('Code Injection') vulnerability in Mohammad I. Okfie IF AS Shortcode if-as-shortcode allows Code Injection.This issue affects IF AS Shortcode: from n/a through <= 1.2.

NVD CVE-2025-68897 Patchstack advisory

Recent activity

2024-08-09 — latest release on wordpress.org (1.2).
2025-12-29 — Remote code execution disclosed (CVE-2025-68897), no fix listed yet.

Free. We check the CVE feeds every day and email you only when a new issue for IF AS Shortcode (if-as-shortcode) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Remote code execution (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/if-as-shortcode (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/if-as-shortcode"><img src="https://laskyr.com/plugins/if-as-shortcode/badge.svg" alt="IF AS Shortcode vulnerability status"></a>

← Check another plugin · Free hacked-site scan