No Code Attached Yet
avatar TawareAditya
TawareAditya
22 Feb 2025

Steps-

  1. Create 2 articles with a Super admin login. Set 1 article with Super Admin access and the other with public or registered access.
  2. Now log in with the Administrator user/role. Go to the article list page.
  3. Open the inspector and replace the value of the article set for the Super Admin access level.
  4. Click the status icon.
  5. You can see the Super Admin access level article status get updated.

Expected result

Should check the access level and server-side validation.

Actual result

System information (as much as possible)

Additional comments

The same can reproduce using the Burp Suite application

Votes

# of Users Experiencing Issue
0/1
Average Importance Score
1.00

avatar TawareAditya TawareAditya - open - 22 Feb 2025
avatar TawareAditya TawareAditya - change - 22 Feb 2025
Labels Removed: ?
avatar joomla-cms-bot joomla-cms-bot - change - 22 Feb 2025
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 22 Feb 2025
avatar SniperSister
SniperSister - comment - 22 Feb 2025

Two things:

  1. findings with a potential security-impact should always be reported to security@joomla.org, not in public tracker tickets
  2. you are mixing access levels (which control view permissions) with ACL permissions. Permissions control what a user can do (create, update, delete etc), while access levels control what users see. It might seem counter-intuitive, but these two systems work independently from each other and therefore it's currently expected behavior that you can update the state of an entity that you can't see because the view levels mismatch.

So, I would suggest to close this issue.

avatar chmst chmst - change - 24 Feb 2025
Status New Closed
Closed_Date 0000-00-00 00:00:00 2025-02-24 10:22:15
Closed_By chmst
avatar chmst chmst - close - 24 Feb 2025
avatar chmst
chmst - comment - 24 Feb 2025

@TawareAditya thank you for your interest in Joomla.
As @SniperSister explains, this is a misunderstanding. So I close this and your other issues.

Add a Comment

Login with GitHub to post a comment