wordpress-block-editor-fse

skills-sh:bobmatnyc_claude-mpm-skills__wordpress-block-editor-fse

View source
F
0/100

First Seen

Feb 18, 2026

Last Scanned

Feb 20, 2026

Findings

18

Score

0/100

HIGH 14
MEDIUM 1
LOW 3

Findings (18)

HIGH
Hidden HTML comment contains action verbs
L583

Hidden HTML comment contains action verbs

<!-- wp:post-title {"level":1} /-->
FIX

Remove hidden text (e.g., HTML comments with directives, zero-width characters, white-on-white text). All content should be visible and explicit in the skill definition.

FP?

Likely FP if the match is a standard HTML comment used for code documentation, or base64 content used for legitimate data encoding (e.g., images).

HIGH
Hidden HTML comment contains action verbs
L584

Hidden HTML comment contains action verbs

<!-- wp:post-featured-image /-->
FIX

Remove hidden text (e.g., HTML comments with directives, zero-width characters, white-on-white text). All content should be visible and explicit in the skill definition.

FP?

Likely FP if the match is a standard HTML comment used for code documentation, or base64 content used for legitimate data encoding (e.g., images).

HIGH
Hidden HTML comment contains action verbs
L585

Hidden HTML comment contains action verbs

<!-- wp:post-content /-->
FIX

Remove hidden text (e.g., HTML comments with directives, zero-width characters, white-on-white text). All content should be visible and explicit in the skill definition.

FP?

Likely FP if the match is a standard HTML comment used for code documentation, or base64 content used for legitimate data encoding (e.g., images).

HIGH
Hidden HTML comment contains action verbs
L586

Hidden HTML comment contains action verbs

<!-- wp:post-date /-->
FIX

Remove hidden text (e.g., HTML comments with directives, zero-width characters, white-on-white text). All content should be visible and explicit in the skill definition.

FP?

Likely FP if the match is a standard HTML comment used for code documentation, or base64 content used for legitimate data encoding (e.g., images).

HIGH
Hidden HTML comment contains action verbs
L603

Hidden HTML comment contains action verbs

<!-- wp:query {"queryId":1,"query":{"perPage":10,"postType":"post"}} -->
FIX

Remove hidden text (e.g., HTML comments with directives, zero-width characters, white-on-white text). All content should be visible and explicit in the skill definition.

FP?

Likely FP if the match is a standard HTML comment used for code documentation, or base64 content used for legitimate data encoding (e.g., images).

HIGH
Hidden HTML comment contains action verbs
L612

Hidden HTML comment contains action verbs

<!-- wp:post-template {"layout":{"type":"grid","columnCount":3}} -->
FIX

Remove hidden text (e.g., HTML comments with directives, zero-width characters, white-on-white text). All content should be visible and explicit in the skill definition.

FP?

Likely FP if the match is a standard HTML comment used for code documentation, or base64 content used for legitimate data encoding (e.g., images).

HIGH
Hidden HTML comment contains action verbs
L613

Hidden HTML comment contains action verbs

<!-- wp:post-featured-image {"isLink":true} /-->
FIX

Remove hidden text (e.g., HTML comments with directives, zero-width characters, white-on-white text). All content should be visible and explicit in the skill definition.

FP?

Likely FP if the match is a standard HTML comment used for code documentation, or base64 content used for legitimate data encoding (e.g., images).

HIGH
Hidden HTML comment contains action verbs
L614

Hidden HTML comment contains action verbs

<!-- wp:post-title {"isLink":true} /-->
FIX

Remove hidden text (e.g., HTML comments with directives, zero-width characters, white-on-white text). All content should be visible and explicit in the skill definition.

FP?

Likely FP if the match is a standard HTML comment used for code documentation, or base64 content used for legitimate data encoding (e.g., images).

HIGH
Hidden HTML comment contains action verbs
L615

Hidden HTML comment contains action verbs

<!-- wp:post-excerpt /-->
FIX

Remove hidden text (e.g., HTML comments with directives, zero-width characters, white-on-white text). All content should be visible and explicit in the skill definition.

FP?

Likely FP if the match is a standard HTML comment used for code documentation, or base64 content used for legitimate data encoding (e.g., images).

HIGH
Hidden HTML comment contains action verbs
L616

Hidden HTML comment contains action verbs

<!-- /wp:post-template -->
FIX

Remove hidden text (e.g., HTML comments with directives, zero-width characters, white-on-white text). All content should be visible and explicit in the skill definition.

FP?

Likely FP if the match is a standard HTML comment used for code documentation, or base64 content used for legitimate data encoding (e.g., images).

HIGH
Hidden HTML comment contains action verbs
L2245

Hidden HTML comment contains action verbs

<!-- wp:post-title /-->
FIX

Remove hidden text (e.g., HTML comments with directives, zero-width characters, white-on-white text). All content should be visible and explicit in the skill definition.

FP?

Likely FP if the match is a standard HTML comment used for code documentation, or base64 content used for legitimate data encoding (e.g., images).

HIGH
Hidden HTML comment contains action verbs
L2247

Hidden HTML comment contains action verbs

<!-- wp:post-content /-->
FIX

Remove hidden text (e.g., HTML comments with directives, zero-width characters, white-on-white text). All content should be visible and explicit in the skill definition.

FP?

Likely FP if the match is a standard HTML comment used for code documentation, or base64 content used for legitimate data encoding (e.g., images).

HIGH
Hidden HTML comment contains action verbs
L2249

Hidden HTML comment contains action verbs

<!-- wp:post-featured-image /-->
FIX

Remove hidden text (e.g., HTML comments with directives, zero-width characters, white-on-white text). All content should be visible and explicit in the skill definition.

FP?

Likely FP if the match is a standard HTML comment used for code documentation, or base64 content used for legitimate data encoding (e.g., images).

HIGH
Hidden HTML comment contains action verbs
L2251

Hidden HTML comment contains action verbs

<!-- wp:post-date /-->
FIX

Remove hidden text (e.g., HTML comments with directives, zero-width characters, white-on-white text). All content should be visible and explicit in the skill definition.

FP?

Likely FP if the match is a standard HTML comment used for code documentation, or base64 content used for legitimate data encoding (e.g., images).

MEDIUM
Non-standard port communication
L2235

Detects outbound connections to non-standard ports

http://localhost:8888
FIX

Restrict network connections to standard ports (80, 443) and explicitly allowlisted service ports. Block connections to unusual ports that could indicate covert channels.

FP?

Likely FP if the non-standard port is localhost (127.0.0.1) used for local development servers (e.g., port 3000, 8080, 5432 for a local database).

LOW
Unverified npx package execution
L2234

Detects npx executing packages from unverified sources without pinned versions

npx @wordpress/env 
FIX

Pin the npx package to an exact version (e.g., npx @scope/package@1.2.3). Unversioned npx commands can silently install a different or malicious package version.

FP?

Likely FP if the npx command targets a well-known package in documentation context, though unpinned versions are a real supply chain concern.

LOW
Unverified npx package execution
L2237

Detects npx executing packages from unverified sources without pinned versions

npx @wordpress/env 
FIX

Pin the npx package to an exact version (e.g., npx @scope/package@1.2.3). Unversioned npx commands can silently install a different or malicious package version.

FP?

Likely FP if the npx command targets a well-known package in documentation context, though unpinned versions are a real supply chain concern.

LOW
Unverified npx package execution
L2238

Detects npx executing packages from unverified sources without pinned versions

npx @wordpress/env 
FIX

Pin the npx package to an exact version (e.g., npx @scope/package@1.2.3). Unversioned npx commands can silently install a different or malicious package version.

FP?

Likely FP if the npx command targets a well-known package in documentation context, though unpinned versions are a real supply chain concern.