XTemos Blog widget display malfunction

Hello Support, relative novice here. I am having a display problem with the XTemos Blog widget.

Problem: “My ‘Featured Recipes’ section on the homepage for my site https://eathenet.com/ (using the XTemos Blog widget) displays incorrect images (from my homepage) and the Continue Reading element links (to my homepage) instead of the actual recipe post data. It looks correct in the Elementor editor, but not on the live site.”
Key Details from my Investigation:
“The widget’s query settings (Category: Recipes, Order by: Random) are correctly configured in Elementor.”
“I have cleared all caching layers (WP Rocket, server-side, browser, CDN).”
“Elementor Safe Mode did not resolve the issue.”
“I inspected the live HTML, and confirmed the src and href attributes are explicitly pointing to my homepage URL (https://eathenet.com/), not the recipe post URLs.”

Analysis of the Live HTML Output
The HTML confirms exactly what’s happening on your live site:
Image ( tag): The src attribute is explicitly pointing to https://eathenet.com/wp-content/uploads/2020/01/San-Antonio-mexican-restaurant.jpg. This is indeed an image from your homepage (specifically, the “Welcome to Eathenet” page, with data-attachment-id=”940″).
Links ( tags): Both the href attribute for the image wrapper () and the “Continue reading” link () are explicitly set to https://eathenet.com/.
Woodmart Classes: The presence of classes like wd-post-img, wd-post-read-more, wd-fill confirms that this is indeed a Woodmart-specific widget generating this content.
What this means:
The XTemos blog widget (or whatever it’s called exactly) is failing to correctly retrieve the dynamic data (featured image URL and post permalink) for the recipe posts it’s querying. Instead, it’s falling back to some default context, which appears to be the homepage’s featured image and URL.
“I tested by adding a brand new instance of the same widget to a new section, configuring it identically, and it exhibited the exact same incorrect behavior on the live site. This confirms the issue is with the widget itself, not just a corrupted instance.”
Crucial Context: “My site previously experienced breakages when Elementor Pro was activated, and it has since been deactivated. I am currently running Elementor Free.”

Thank you